Add support for NotAny join operator in Query Expression #281
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements support for the
NotAnyjoin operator in XrmMockup Query Expression, addressing the limitation where onlyLeftOuterjoin was previously supported.What was implemented
The
NotAnyjoin operator provides anti-join functionality, returning records from the primary entity that do NOT have matching records in the linked entity.Key changes:
FetchXML parsing support - Added
"notany"link-type parsing inXmlHandling.cs:Query Expression support - Added
JoinOperator.NotAnyhandling inRetrieveMultipleRequestHandler.cs:Anti-join logic - Implemented proper NotAny behavior:
Example usage
Testing
Added comprehensive test coverage including both QueryExpression and FetchXML scenarios. The implementation follows the same patterns as existing join operators and maintains full backward compatibility.
Fixes #280.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.