The top Connect item for MSDynCRM requesting NOT-IN functionality is resolved, if you consider coding/development requirements as user friendly enough.
https://connect.microsoft.com/dynamicssuggestions/Feedback/Details/678568
Using tools such as FetchXML Builder (google it if you don't know it) you can alter views to introduce not-in behaviour.
However - when you select a not-in view as source for a dynamic marketing list, CRM removes everything related to the not-in behaviour from the query.
So not even coding / query injecting works here.
That really should be fixed, even if it is not possible to render the "UI" for the query, it should at still keep the query that is retrieved from the selected view, possibly with a message that "This query is too complex possible to display in the query designer, would you like to use it anyway?"
There is really no reason the Dynamic ML should not work with complex queries.
Comments
Additional info: Updating the ML query using the SDK breaks the ML recipient view entirely, with an incorrect message such as 'Account' entity doesn't contain attribute with Name = 'contactid'. This was from the fairly simple and straight-forward query: <fetch version="1.0" output-format="xml-platform" mapping="logical" distinct="false" > <entity name="account" > <attribute name="name" /> <attribute name="telephone1" /> <attribute name="accountid" /> <filter> <condition attribute="statecode" operator="eq" value="0" /> <condition entityname="subcontacts" attribute="contactid" operator="null" /> </filter> <order attribute="name" descending="false" /> <link-entity name="contact" from="parentcustomerid" to="accountid" link-type="outer" alias="subcontacts" /> </entity> </fetch> This is IF you use an alias for the outer join link-entity. Workaround, not very pleasant, is to skip aliases for outer join links.
Category: General
Administrator on 11/27/2023 4:47:05 PM
Thank you for submitting your idea to our ideas portal. We appreciate your contribution and the time you took to share it with us. We have shipped many enhancements since this idea was posted and it is likely that it has been resolved. If not, kindly reopen. Thank you again for your continued support.