-
Notifications
You must be signed in to change notification settings - Fork 626
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
SetLoadFields, SetAutoCalcFields, IsEmtpy #25084
SetLoadFields, SetAutoCalcFields, IsEmtpy #25084
Conversation
Apps/W1/EssentialBusinessHeadlines/app/src/codeunits/EssBusHeadlineSubscribers.Codeunit.al
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great performance optimization! I'll process this one right away and get it ready for 23.2 (I think 23.1 has sailed).
Apps/W1/EssentialBusinessHeadlines/app/src/codeunits/EssBusHeadlineSubscribers.Codeunit.al
Show resolved
Hide resolved
Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one. Build ID: 13545. |
Availability update: We will publish a fix for this issue in the next update for release 23. Build ID to track: 13938. |
We have some longrunning SQL Statements and Methods as well as Deadlocks and Locktimeouts with the Headlines Executor. I looked into it and found that there are possible optimizations for example an IsEmpty before a deleteall, Calcfields in a Reapeat-Until instead of SetAutoCalcFields and SetLoadFields on some older headline procedures. I would prefer a to add TopNumberOfRows at the TopCustomer Query, but this would break the feature I think.
We have some longrunning SQL Statements and Methods as well as Deadlocks and Locktimeouts with the Headlines Executor.
I looked into it and found that there are possible optimizations for example an IsEmpty before a deleteall, Calcfields in a Reapeat-Until instead of SetAutoCalcFields and SetLoadFields on some older headline procedures.
I would prefer a to add TopNumberOfRows at the TopCustomer Query, but this would break the feature I think.