Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Karli Mather]

Hi,

I was wondering why almost always AX uses one design per DyamicsAxModelProject? Is this because it would be hard to find the project to debug and fix? If this is the case, couldn’t we just group it like the menus are grouped (AP reports, AR reports, etc?) I know we can specify different data sets per design so it’s not like the data available to the reports would get unnecessarily bulky.

Thank you,
Karli

——————————
Karli Mather
Fidelitone
Wauconda IL
——————————

[Corey Vantilborg]

The primary reason is to break the code into manageable chunks which allows for easy layer comparison, and XPO management.  This further allows multiple developers to work on different reports at the same time.  

Since most reports are bound to a data provider and contract,  this further encourages breaking reports into single purposes.  There certainly are native reports containing multiple designs,  though they tend to be different expressions of the same purpose. 

There is nothing stopping you from stuffing all of your custom reports into a single project, and managing which data provider methods run based on the data contract.   However I don’t know why you would do this.  

——————————
Corey Vantilborg
ERP Analyst
Tigercat International Inc.
Brantford ON
——————————
——————————————-

[Karli Mather]

Corey,

Thanks, I was asked this by someone in my organization, which is new to AX and I couldn’t come up with a good answer besides “reports are sometimes difficult to find and work in due to the sheer number of base reports in AX and further grouping might further complicate.”

——————————
Karli Mather
Fidelitone
Wauconda IL
——————————
——————————————-