-
Notifications
You must be signed in to change notification settings - Fork 34
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
Missing actions in generated model files #413
Labels
bug
Something isn't working
Comments
I have a similar issue. In August 2022 it worked but not anymore. If developers need more details, I can send privately. |
We have identified and resolved this issue... the fix for this will be included in the next drop. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have the problem with
pac modelbuilder build
verb on an environment with a lot of entities - in my case, I'm using Dynamics CRM + Omnichannel + Marketing + Portal. The command used is e.g.the result (please note: 136 messages and only 2 actions written to files):
but with some sample message filtering:
the result (please note: 859 messages and 821 actions written to files):
I believe the root cause of the issue is the fetchxml which pac is using to query Dataverse for messages:
After testing this query, it doesn't return paging-cookie, which implies a limit of 50k records - https://learn.microsoft.com/en-us/power-apps/developer/data-platform/org-service/paging-behaviors-and-ordering#legacy-paging .. A slight modification of the query (m internal order - in sdkmessagerequestfield link-entity) after execution returns a paging cookie:
.. but maybe such modification can affect the non-deterministic resultset (https://learn.microsoft.com/en-us/power-apps/developer/data-platform/org-service/paging-behaviors-and-ordering#ordering-and-multiple-table-queries). Perhaps a better solution would be built-in exclusion of standard messages like Create, Update, Delete and so on.
The issue also applies to the crmsvcutil.exe tool and other tools that use it, e.g. daryllabar/DLaB.Xrm.XrmToolBoxTools#307
The text was updated successfully, but these errors were encountered: