Microsoft Dynamics 365

Cache Lookup Caches are used on both the client and the server. It increases the performance, the ax will get data from the cache instead of doing round trips and DB calls. So for each table, it's good to use cache lookup property.Microsoft Dynamics Ax run time manages the cache by removing old records when new records are added to the cache. Client Cache A Client-side cache can be used only by the client. The client cache is used when a select statement is executed from the client tier. If no records are found in the client cache, the client then searches in the server cache for the records. If the record isn't located in the server cache, it will retrieve from the database. The maximum number of records can be maintained in a client cache is 100 records per table for the selected company. Server Cache A server-side cache can be used by any connection to the server. The server cache is used when a select is executed on the server tier. If no record found in th

D365 features a new framework called the date effective framework, or valid time state tables. There are many easy examples of date effective data. The easy example is some sort of rate table, where rates become effective and expire at certain times. Other examples could be bills of material or revisions of items that become effective or expire at certain dates. Date effective comes in two flavors. One uses regular date fields, the other UtcDateTime data type. Obviously, the UtcDateTime gives you more granularity to the second (and the nice timezone support that comes with UtcDatetime). For this example, we'll just stick with an easy example using regular dates. First, we create a new table and we'll call it LeaveRequest table. We'll give the table a LeaveRequestID field which identifies the different request ID. On the table's properties, we'll set the ValidTimeStateFieldType to "Date". This will automatically create two new date fields called "