2
We are currently rolling out D365 HR globally and have approximately 70 different legal entities to migrate data for.
As a result, even though we have the same data source, we have to produce 70 different import files for the same entity.
If there was an extra field on each entity to specify want company to process the record for, it would save hundreds of hours of effort.
As a result, even though we have the same data source, we have to produce 70 different import files for the same entity.
If there was an extra field on each entity to specify want company to process the record for, it would save hundreds of hours of effort.
STATUS DETAILS
Declined
Comments
What are you talking about? I'm not talking exporting? I'm talking about importing data from an external data system into D365. Azure Data Lake has nothing to do with this scenario
Category: Data Management
Sunil Garg (administrator) on 5/8/2020 3:22:32 PM
The integration with Azure Data Lake will allow for exporting data from one or more companies without having to create any export jobs. That should address this scenario.
Hope this helps.
Thanks.