In this video I take a look at using the data management work space to import data into Dynamics 365 Finance and Operations. --Feel free to follow me in LinkedIn / scottmgaines
Hey there ..Gr8 work. I want to know about auto entity sequencing. Microsoft has provided default templated with data import sequence. E.g. vendor group should be imported before vendor master. If we have custom entities, can we somehow auto sequence them without assigning sequence number manually. There is a feature available but it often given an error message especially when there are so many entities to auto sequence
@@Scott-Gaines I found this discussion thread that is about sequencing the FIELDS on a custom entity, but there is information in there that implies there is also a 'sequence' field on the entity that allows you to set it's sequence with a data project. "The 'sequence' field refers to the sequence of importing the data entities and not to how the fields appear." I looked for reference to that in Microsoft's documentation about creating custom entities and I didn't find any reference to a 'sequence' field. I do see in Microsoft's documentation about creating templates, that "Our long-term goal for sequencing is to automatically sequence all the entities for every configuration. Until we reach that goal, for the entities in each of our default templates, we have created sequences that represent the dependency order between entities." So if they can set the sequencing for their entities, it seems a developer should also be able to do this for a custom entity docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/configuration-data-templates#sequencing-in-the-default-templates Sorry this answer is incomplete, but I'm not a developer so this is just from searching documentation. Good Luck!
I have another question... You show creating your export project with "Skip Staging" = No. I don't see that same choice when you create import project. However, when you did the export, the data was immediately available for download. You didn't have to go to the staging table and request the download. And on the import side, the new or changed Locations were immediately available in the entity without having to do two steps (first to staging, then staging to target), but yet in your example where you forced an error then the data was in the staging table. I'm confused about this. If using staging tables, why isn't it always a two step process, both to export and import? (Believe me, that would be a pain and I don't wish it that way, but I thought that is how it worked until I watched your video!)
Yes that skip staging is a default. That just determines if the data goes into a staging table prior to export. In a lot of cases you'll get a message saying staging cannot be skipped and the flag will be checked. On the import side things always go into staging that way if there's an error you can fix the issue without having to reupload. I believe I show this in the upload video I gave you in your other comment.
I've watched your import video and your one about templates. What I'm not clear on is how to combine the two. How can I create an import project from a template to add all the right entities to my project, and then attach the correct import file to each line? You show here deleting the entity from the project and re-adding it, so that defeats the purpose of having a template. I thought maybe I have to save the input file names with the template and then call the input file by the same name each time I create a project from the template, but I couldn't find that either.
I just watched your export video and you said you were going to cover how to import using a data package. Will you be covering that in an other video? I'm not sure this answers my above question, but it might.
Here's the one for the import... ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-Zlvb_lR-O0g.html The template is mainly used for the export. So the process is to add the template to the export. On the export create a package. This will be a zip file of all the entities that are in the template. Then on the import side you select the package file to import.
