Export And Import Data Entity for OData


1. Make sure that you opened Visual studio as administrator.

2. Also check that your module is referring to basic models like ApplicationSuite, Application Foundation, etc.

3. Create a new Dynamics 365 project.

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

5. Select the table you want for your entity in the Primary Datasource option

6. Select Entity Category either Document or Master.

Click next, now it creates the entity along with the other required stuff.

Build and sync project.

Exposing as Json file:

Below mentioned URL will be used for checking any exposed data entity.  But you need to concatenate the public collection name of your data entity at the end of  the URL

https://usnconeboxax1aos.cloud.onebox.dynamics.com/data/DataentityPublicCollectionName

Note: the link may differ according to your company domain.

 For verification, you may use this URL on IE or chrome and it will generate JSON file. 

 Exporting from Data Management:

Create a new group, add some description. Select Your Entity and the format you want for your data Add and then click the export button. And finally, click on Export Now

Sometimes this downloading stuck or take a lot of time so make sure your service is running or restart it.


Importing from Data Management:

Create a new group, add some descriptions. Select Your Entity and the format in which your data is. Select the file you want to import Upload and Add and then click the import button. And finally, click on Import Now

In case your import or export is unsuccessful view the execution log for the errors and tries to figure out the problem.

In my case the duplication problem occurs as the index fails to make the record unique, so I need to add a new index in the table.

Also, check the stagging table for data. Empty in my case.


After making changes in your table make sure these changes also reflect in the entity for this first Restore the entity and the update the Stagging table. If the changes still not reflecting, then delete the stagging table and regenerate it.

Entities usually not pick the changes immediately so for making sure that your changes are picked up Click on the Data Entity tile.

And select your Entity make sure any group is not using it at that time then Delete it and then sync and rebuild your project.

Click on the framework tile for refreshing the changes

Now re-import the entity. Voila, it worked!!



 

Comments

Post a Comment

Popular posts from this blog

Batch jobs stuck on WAITING status in AX 2012

Image
Step1 . Generate incremental CIL Step2 . Check if any batch job is stuck on “ executing status ”, change its status to withhold or cancel.  Because it can be possible that all the new batch jobs are stuck on “ Waiting ” because any previous job is stuck on executing. Also, do the same for other “ waiting ” jobs Step3 . Now check the assigned batch group in your job and then check if that batch group has correct AOS server assigned and then check that if the check box named: ' Is batch server ' checked for that particular AOS server . Also, the time should be 12.00.00 to11.59.59 System administration  à Setup  à Server Configuration: either the AOS server assigned to the batch group is not marked as the batch server or else the batch group is not assigned to the batch job. System administration  à Setup  à Batch group Now run any batch job. It will not be stuck in waiting status.  
Read more

Electronic Reporting For Beginners

Image
  Basics of Electronic Reporting & Business Documents in D365 F&O Introduction: Electronic reporting is a no-code reporting tool that is completely integrated into D365.  It allows the creation of report structures directly within the platform without the need for extra software like Visual Studio.  Customization of business documents using Excel is also feasible, this is a great alternative for non-developers.  C onfigurations from the Life Cycle Services (LCS) asset library can be easily downloaded  and loaded into D365FO for use in reports and print management. Visual editors are used to create all components of the ER configuration. The language that is used for data transformation resembles the language that is used in Microsoft Excel. Data flow: Component ER supports the following types of components: Data model Model mapping Format Metadata Designing: Go to the path:  Organization administration > Workspace >Electronic Rep...
Read more

Computed column and virtual field in D365

Image
  Computed column and virtual field: Requirement: Display methods needed in entity/view Solution: There are two different approaches for adding additional  unmapped  fields beyond those that are directly mapped to fields of the data sources. 1.        Computed column (SQL query executed by Microsoft SQL Server) 2.        Virtual Field (Custom X++ code)   ·       Computed Column: The computed column method returns a T-SQL query. It hits during database synchronization and is written to the database. In runtime no x++ code is executed, instead, your T-SQL query is executed inside the database. It is mostly used for reads/exports. Performance wise it is better than virtual methods. Equivalent X++ query: select sum (amount) from consignmentProductReceiptJournalLine           where consignmentProductReceiptJournalLine.ReplenishmentOrderLine =...
Read more