You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When a project containing multiple entities (100+) defined on same level, unit and sequence get exported using DMF UI action ExportAsync the entities are exported simultaneously, depending on allowed threads by AOS. When using the ExportToPackage API - or job type Export in RIS - the entities are exported one by one and we don't leverage the available threads. Am I missing a flight feature in D365, or parameter in RIS?
Describe the solution you'd like
A method to allow exports on demand scheduled by RIS and using the capabilities of multithreaded exports is desirable.
Describe alternatives you've considered
Using job type Download, but by using Download we receive the latest packages as scheduled in D365 and not live data on demand. As stated in wiki, jobs of type Export are recommended
Flighting feature DMFExportToPackageForceSync is set to asynchronous by default, we haven't changed this flag as asynchronous would be preferred
Additional context
Behaviour when exporting a project with action "ExportAsync" in DMF UI
Behaviour when using ExportToPackage API
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When a project containing multiple entities (100+) defined on same level, unit and sequence get exported using DMF UI action ExportAsync the entities are exported simultaneously, depending on allowed threads by AOS. When using the ExportToPackage API - or job type Export in RIS - the entities are exported one by one and we don't leverage the available threads. Am I missing a flight feature in D365, or parameter in RIS?
Describe the solution you'd like
A method to allow exports on demand scheduled by RIS and using the capabilities of multithreaded exports is desirable.
Describe alternatives you've considered
Using job type Download, but by using Download we receive the latest packages as scheduled in D365 and not live data on demand. As stated in wiki, jobs of type Export are recommended
Flighting feature DMFExportToPackageForceSync is set to asynchronous by default, we haven't changed this flag as asynchronous would be preferred
Additional context
Behaviour when exporting a project with action "ExportAsync" in DMF UI
Behaviour when using ExportToPackage API
The text was updated successfully, but these errors were encountered: