I think that everyone of you already knows that when working with Dynamics 365 Business Central, table extensions are killers for performances. But how much?
That’s a question that I’ve also done to myself a lot of time when working with partners or when creating my own solutions. Is there a “deadline” for how many table extensions can I create for the same table in order to not kill my performances?
In this video, I show how to work with the AL Table Proxy Generator to create custom integration to Microsoft Dynamics 365 CRM/CE/For sales
A cool feature of the Business Central platform are the virtual tables. Virtual tables can give you data on demand, in this video I showcase a couple of them.
When developing extensions for AppSource, every partner has its own licensing model. There are extensions that are free, others that are billed by users, others that have a fixed price for each month or year of usage and so on. Everyone can have its own way of billing their customers for using an extension. But there are also some extensions that are billed for the number of generated records on a period (electronic document transmissions for example often works on this way).
Table Locking is a very common problem in Microsoft Dynamics 365 NAV / Business Central. If the problem is understood correctly and the right technique is used, Locking Errors can be solved very easily. This post explains different techniques that can be used to solve Locking errors.
Recently Microsoft added the Table Information page to Business Central. See here. And underlying are these objects: Table Information (8700, List) Table Information (2000000028) So I was thinking, hey let’s use this in Power BI.
Recently James Crowter wrote an excellent article about table extensions and how they affect performance. In short, table extensions are great for flexibility and ease of development, but performance decreases when the number of table extensions is adding up. Especially when table extensions are used for hot tables. With hot tables I mean tables that are used often, like Item, Customer, Sales Line, Item Ledger Entry, etc.
Source : Kauffmann @ Dynamics 365 Business Central
Read more…