Tip #374: NOT IN for the rest of us

Those with black belt in XML are familiar with the technique of building a FetchXML expression for NOT IN clause (e.g. accounts with no activities) and then sneaking that XML into a view definition to create non-editable view that returns the desired results.

What about the rest of us who don’t have the skillz or guts to edit customization.xml file?

  • Add a rollup field that counts the child records
  • Build a view that returns records where this field is zero

It’s not a real-time condition but is simple to build and use. In addition, the counter can be used as a quick visual indicator on the form itself if, for example, child records are not in the readily available subgrid.

Note: This tip was actually produced by Joel but since he’s too buzy or lazy to put this in writing, I’m taking all the credit.

Share on FacebookTweet about this on TwitterShare on Google+

One thought on “Tip #374: NOT IN for the rest of us

  1. […] even editing the customisation file directly. There is also the rollup field approach described in http://crmtipoftheday.com/2015/04/27/not-in-for-the-rest-of-us/. But if you are going to do an ad-hoc advanced find query, you really don’t want to create […]

Leave a Reply

Your email address will not be published. Required fields are marked *