- The article discusses the impact of using the ER model mapping table method on the performance of Microsoft business applications like Dynamics 365.
- When the table method is used, such as in the provided example, the salesTable() method is executed three times per each record.
- This can negatively affect the performance when executing other logic and calling it from a large number of records.
- The article suggests using a Calculated Field as an easy solution to improve performance.
- By creating a Calculated Field and calling it directly, the salesTable() method is only called two times, one per each record.
- It is recommended to save reused methods into Calculated Fields to avoid unnecessary calls in Electronic Reporting.
- The article encourages readers to watch a video for further clarification on using Calculated Fields.
- The author concludes by expressing hope that the readers found the information helpful.
Registered users can view the full text for FREE!
Sign In Now!
