Replies: 1 comment
-
I think this has no answer... 😕 N:N is actually N:1:N, even if you filter it like your query, technically you are locked into the relationships... (I may have misunderstood everything - if so, please correct me!) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Curious if anyone has a clever way of using fetchxml to flatten out data for an N:N relationship. I can achieve it with a 1:N but not an N:N
Desired outcome would look like below (note the link entity and alias)
The above eliminates multiple duplicate rows with the following fetchxml against 1:N relationship.
But I cannot achieve the same thing when using an OOTB N:N Relationship as it duplicates records for each occurrence of related records.
Thanks
Guy
Beta Was this translation helpful? Give feedback.
All reactions