BEWARE:   is rebranded to     The STAEDEAN documentation for products related to  Microsoft Dynamics 365 for Finance and Supply Chain Management is moved to docs.staedean.com.   The Data modeling studio documentation is moved to Data Modeling Studio. The documentation on docs.to-increase.com is no longer updated.

 

Data modeling studio for Microsoft Dynamics 365 for Finance and Operations offers capabilities to export large volumes of data with high speed from D365 FO.

The data is exported to a BYOD (bring-your-own-database) from where it can be picked up by a data warehouse. You can use this data, for example, for analytics purposes.

This picture gives a schematic overview of how Data modeling studio (DMS) is positioned:

In the Data modeling studio:

• Data sets define the data to be exported by a data model. A data set is related a specific table and contains the applicable fields which data must be exported.

   

• Data models define the data to be exported. A data model contains the data sets and data entities for the data export scenario.

If you can't find the information you are looking for, you can:

 

• Visit our portal to explore our knowledge base, raise a question, or report an issue.
• Get in contact with us.
• Provide feedback on the documentation, using the 'Provide feedback' button at the bottom-left of a content page.

Setting up and maintaining Data modeling studio

In the Data modeling studio, you can use:

• Data sets to define the data to be exported by a data model. For each data set, define the relevant table and fields.
• Data models to define the data to be exported.

• Data templates to exchange data modelling configurations.

• Transformations to define SQL statements that can be executed on deploy or export of a data model.

Processing and monitoring data exchange

If a data model is set up and deployed, you can export the data as defined in the data model.

During data export, actions are logged. You can monitor the data export actions.