Number of dimension values specified is different from the number setup in the active format for data entities

Lets discuss about the one of the issue (Number of dimension values specified in application development is different  from the number setup in the active format for data entities ) which anyone might face while import or export operations using entities.
Lets assume there is one of the common scenario in which you are uploading records for customer groups  along with its  financial dimensions using data entities.

Problem : Number of dimension values specified in application development is different  from the number setup in the active format for data entities.

Root cause :  There is difference in number setup of  excel file and active format of data entities.

Solution : Check your active format for financial dimension on following navigation (General ledger - Charts of accounts - Dimensions - Financial dimension configuration for integrating applications) and update excel file according to format or change its format. Then try to import data by using entity.

Below is the file format for customer groups uploading process through entities. For dimension value we are using  format Dimension1-Dimension2-Dimension3.

Accelerate data import process by using entity execution parameters

Lets discuss about execution parameters which are found in the Data import/export framework parameters. They can be used for speeding up data import process in order to optimize the performance when large number of records are uploaded using data management features.

As we all know that in Dynamics AX 2012 we used to define number of tasks at a creation of processing group. While here in D365 they are moved to Data import/export framework parameters.
Basically it is an option which provides information of dividing workload whenever we are performing records upload in bulk by using batch framework.
Lets begin with a scenario of  uploading sales order lines  in bulk. So, here we need to divide this upload process into sub tasks for better performance. For this purpose we need to follow some steps.

1. Open entity execution parameters by navigating on this path : Work spaces -> Data Management -> Framework parameters tile -> Entity settings -> Configure entity execution parameters

2. After clicking configure entity execution parameter, a screen will appear where we can add our entity.

• Entity : Entity name will be selected from drop down and it will be used here for further process.
• Import threshold record count : Here we can specify a threshold per entity when the tasks need to split and how many task will be created. For instance in below example 500 records will be processed per task. 
• Import task count :  It will create multiple threads where the workload will be divided and run in parallel. For instance in below example 20 threads will be created.

3. Now its time to import the records in batch. For this navigate to Work spaces -> Data management -> Import tile 

Add all required details here for upload process and go on Import options -> Import in batch.

You process will be started and it will upload records in batch, You can monitor how many tasks are created on the View tasks form at a time of  execution of batch job. 

Note : It is not necessary that all entities will be supported for multiple task. See below screen shot like vendors entity is not supported for more than one task.

Exposing data entities for OData

Today I will be discussing about to how to expose data entities for OData. First lets talk about what is Odata?

It is a standard protocol for creating and consuming data. Its main purpose is to provide a protocol that is based on Representational State Transfer (REST) for create, read, update and delete (CRUD) operations. It applies web technologies such as HTTP and JSON to provide access to information from various programs.
It provides following benefits.

• Let developers interact with data by using RESTFUL web services.
• Provides a simple and uniform way to share data in a discover able manner.
• Enables broad integration across products.
• Enables integration by using the HTTP protocol stack.

Lets say we have a scenerio in which we are integrating ax with another party for purhcase orders. All PO's will be created in their system and we need to have them in AX. For this purpose we will be creating a data entity which will be exposed publicly for Odata.

1. Open Visual studio as a administrator.

2. I have created DemoModel for it. Below is its screen shot and remember it is new package referring to basic models like ApplicationSuite, Application Foundation etc.

  

3. Create a new project first. By clicking on File -> New -> Project -> Select unified operations from Dynamics 365 node.

4. Create a data entity by right clicking on your project. Add new item -> Data model -> Data entity

5. Select PurchTable in Primary Datasource option.

Note : Public collection name will be publicly used for exposing and i have selected limited number of fields from purchtable. You may select it as per your requirements.

6. New entity has been created along will additional required artifacts 

7. Note all properties and remember to change data entities name label as per your requirements. Because there are chances you might encounter issues while building project since data entity name might be be used by existing entities. .

8. Build and sync project.

9. For verification you may use this URL on IE and it will generate  json file. 

Final result

Note : Below mentioned URL will be used for checking any exposed data entity.  Just you need to add your data entity public collection name.

https://usnconeboxax1aos.cloud.onebox.dynamics.com/data/Data entity public collection name

Import data in D365 using entities

Today i will discussing about how to import data using entities. For this purpose  I will be importing data of customer group by using CustCustomerGroupEntity which is OOTB entity.We have file with following template.

1. Go on Work spaces -> Data Management -> Click on Import Tile button . Select Customer Group Entity in drop down and upload file.

2. Now click on View map of newly uploaded file , map fields ( if required ) and click on save button.

3. Now click on Import button and processing will be started.

4. Keep refreshing and targeted records will be inserted successfully after complete execution.

5. Final output  : Go on navigation -> Accounts receivable -> Setups -> Customer Groups New customer groups created successfully.