March 2020
Intermediate to advanced
534 pages
14h 15m
English
Using the AX 2012 development paradigm, where one is tempted to deploy models to production independently, we might decide to create a package for reports. This would mean we could deliver reports to production, so it may seem natural to create a package that references the main development package. There's some logic to this, but there are two critical problems that mean this method must not be used.
The first problem with this is that any new fields need to be in one package. This could be the main package, requiring one requirement to span packages, or in the reporting package. Any changes in a higher package can't be seen by lower packages: the reference only goes one way.
The second, but much ...
Read now
Unlock full access