Hi @Michelle Jabanes-Oracle and @Tigran Shahnazaryan - yes, Tigran's solution seems to have worked. I think all Leads now display in a single report, regardless as to whether or not they're beyond the Lead stage. Thanks a bunch for helping with this!

@Tigran Shahnazaryan @Michelle Jabanes-Oracle to answer Tigran's question: we would only need to see open Leads combined with Converted Leads that actually started with a Lead record. Since the Lead conversion process allows for merging into an existing Customer at the same time as Opportunity + Task creation, the report…

@Michelle Jabanes-Oracle - I think that's getting closer. I get a total of 47 rows now with that criteria. If I remove the Stage criteria, I still get 47 rows, so I'm not sure that one is needed. Was that in there to filter out Stage = blank? I do know, however, that I have 150 leads in the system, so it doesn't look like…

Hi @Michelle Jabanes-Oracle - thanks for the reply, sorry for the late response! The criteria supplied didn't seem to have the intended effect. I was hoping to have ALL leads show, whether or not they have been converted previously. A mix of converted and open leads. In my particular case, putting in the "System Notes :…

Sorry @Tigran Shahnazaryan - I misinterpreted your reply! This is exactly what I needed, as @Michelle Jabanes-Oracle pointed out. This is great, over in the joined "Applied to Transaction" field selection is a 'Transaction Number', which tracks the originating transaction. As @Brian Stisser points out, this will be tricky…

Thanks @Michelle Jabanes-Oracle - related records! So, let me guess: related records fields are not available within Search/View building. At least, I can't seem to find it.

As always, thanks so much for the info and replies. I'm still missing a piece of the puzzle, but I think I can render it down to just one single question: What is the exact mechanism that links a quote with a sales order? I can't seem to post a table, image, or link into this thread - so I'll just have to type this example…

@Michelle Jabanes-Oracle - thanks for the reply! I'll definitely brush up on Opportunities, but I'm not sure if this was the question I was looking to have answered. I'll see if I can re-phrase: I'm hoping to put together a singular view (to serve as underlying data) that shows only one row for any potential or actual…

@Ivy Lopez-Oracle brilliant - thank you!

@Estee @Ivy Lopez-Oracle - I'm hesitant to start a new topic on these dumb/tiny follow-up questions. But let me know if I should. I'm playing around with field grouping when building searches. But as soon as I change one single field to the summary type Group, then it won't show the results (columns) of any other field…

@Estee @Ivy Lopez-Oracle ah, the "Sales Rep" field! Well.. that's an obvious oversight. That's what I'll use. But knowing about the group summary type is good as well. And then, everything I could newly infer from the HTML formula type criteria, using a <BR> as a delimiter! Thanks for the boost.

Oh, here's an interesting find. @Estee @Ivy Lopez-Oracle With the Main=True flag enabled, it does indeed cut down on the number of duplicate rows. But I had noticed there were still some duplicates. In fact, these duplicates are nearly perfect copies right down to the ID. The ONLY difference is the "Sales Team Member".…

"Main Line" works great! I wonder what other non-field type of criteria functionality is hidden amongst the field names. This is great - thank you both!

@Estee, this is awesome info! This confirms now (thrice over) that the best way to ensure proper ABM lead flow is to pre-emptively create an Opportunity for the rep. But then, how do you ensure the rep doesn't simply ignore the Lead AND Opp, and just go ahead and create their own quote right off the Customer record?…