Skip to content

Clarify 'Select columns' behavior in Dataverse triggers with Dynamics 365 entities #1743

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

FrankFilippini
Copy link

Added a note and example to explain that in Dynamics 365 environments, the 'Select columns' property may not reliably limit flow execution due to system-level processes, plugins, or automatic field inclusion. Also included guidance for using conditional logic to validate actual data changes.

…havior in Dynamics 365 scenarios

Added a note and example to explain that in Dynamics 365 environments, the 'Select columns' property may not reliably limit flow execution due to system-level processes, plugins, or automatic field inclusion. Also included guidance for using conditional logic to validate actual data changes.
Copy link

@FrankFilippini : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit 1a88177:

✅ Validation status: passed

File Status Preview URL Details
articles/dataverse/create-update-delete-trigger.md ✅Succeeded

For more details, please refer to the build report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants