AX 7 has many new features around organizing code; partners, customers, and ISVs need to understand these features to build upgradeable customizations. With prior versions of AX, it was common for customers to get stuck on a version because of the complexity of upgrading.
Keeping AX upgraded benefits customers, ISVs, and Microsoft. Having customers on a more recent code base reduces the cost of maintaining old software versions and the cost of providing support for bugs that have already been fixed.
Having quick and easy access to key project reports and analytics, actions, approvals, and project transaction details can have a major impact on a Project Manager’s ability to successfully deliver on-time and on-budget projects.
The expense reporting feature in Microsoft Dynamics AX includes a number of valuable features!
Entering and approving expense reports is a key part of the client billing and project costing process in many project-driven organizations. To show how fast and easy it really is, SAGlobal has added a video to its demo video library which demonstrates the expense entry process in the new Microsoft Dynamics AX.
There are thirty-two words in the thesaurus for “package”. When the new Dynamics AX (v7) was developed, it seems like everything new was named a package; perhaps it’s because amalgamation does not have the same je ne sais quoi. The nuanced world of Process Data Packages is superfluously delved into forthwith.
Packages. Extensions. Layers. Models. These are important technical concepts in the new Dynamics AX; it is enough to make your head spin. Your future self with thank past self for taking the time to understand how to organize AX code before the first line of code is written