You can imagine a moment when I saw a developer banging his head against the wall…Ī bit more easy was the implementation of the Default dimensions on forms. True, it is more complex than an array field we had before, but we had to learn to use new APIs to get individual dimension values or change values using x++ coding. With only this reference value, it is not known how many dimension attributes you have in the set and which values are set. The default dimension field has a record ID reference to a dimension value set. On a table, you can not directly see the dimension values. A lot of different tables do manage dimension attributes, values, and value sets. The data model and working with dimension APIs was a shock for the existing AX developers ( #XppGroupies). Another benefit was that it did not require a developer to implement more than the standard three dimensions which we had until Microsoft Dynamics AX 2009. Functional, this framework was a relief for many companies as they could set up the financial dimensions without restrictions on the number of dimensions. Microsoft implemented a new data model and dimension framework as part of Microsoft Dynamics AX 2012. This post will not elaborate on these two reasons, but I will explain step-by-step how to create or extend a table and form with ledger default dimension support. At To-Increase, we are developing a new solution where we are looking beyond the standard provided features and there are some interesting questions around the security of the default dimensions. Recently, I got more interest in the ledger default dimensions in Microsoft Dynamics 365 for several reasons.
0 kommentar(er)
