![]() The benefit I see is that I’m not overextending the std Microsoft code. The next step the process does is to take these data and populate the standard 365. Then extracting the data from the C# objects and place the data into a new module I named EPD. I decided to go for a model where D365 is requesting a JSON file from the Swagger API, and then placing the JSON structure in a C# class structure. This would give the best result and the least information loss in the process. Should I just import what I have fields for in D365? Should I extend D365 will lot’s and lot’s of new fields? Or should I model according to how the external database is presenting the data? I decided on the latter and import the data as it was presented. I needed to decide how I should import this data. ![]() To give you a small figure of the complexity you often can find, here is a subset of the JSON hierarchy: We also see that the product databases are quite rich in terms of describing the products with physical dimensions, attributes, packing structure, allergens, nutrition’s etc. Much is different, and the data is often structed differently. One of the experiences I had when starting this journey, is that D365 is not modelled according how the data in these industry specific public databases. Most products is available to the public at VetDuAt.no, but they also have a Swagger API where the JSON data can be fetched and imported to D365. In Norway we have several, and the most common for the grocery industry here is TradeSolution. ![]() Many industries have established vertical specific databases where producers, distributor’s and stores are cooperating and have established standards on product numbers, product naming, GTIN, Global Location Number (GLN) etc. This is not a “Copy-Paste” blogpost, but more show my approach to the process that can be used when working with more advanced and complex JSON integrations. I recently created a solution where I’m importing products and all related data for the grocery industry, and I wanted to share my experience so that others may follow.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |