Make all-company BYOD export one truly all-company export
All-company BYOD export generates sequential exports, company after company. Since 10.0.16 these jobs no longer run in parallel to avoid locks. Downside is that these exports take a lot longer. Suggestion is to change the all-company export into one truly all-company export; fully independent fr...
Modify Dataverse UI to allow multiple F&O virtual entities to be made visible at once
Admin reference for enabling F&O virtual entities in Dataverse - https://experience.dynamics.com/ideas/idea/?ideaid=5a367fe0-b8cd-eb11-ba5e-0003ff45ac2b - makes it clear that each entity that the administrator wishes to enable must be opened individually & made visible with its own checkbox. From...
Allow an option for Supplemental Hierarchy to maintain line items at a Style/Color level
As a clothing Retailer, my company does not maintain pricing at a variant level. We do not sell an Extra-Large shirt for more than a Small shirt of the same color. However, we often place different pricing on different colors of the same style if, for example, one color will not be extended int...
Error handling when importing data with Recurring integrations
It would be a nice improvement if the error handling could show what went wrong when importing data using Recurring integrations. Today it only shows "Processed with error", to figur out what went wrong you need to check the telemetry.
Batch Job/Entity Import Communication
We received an error while running an entity data import in a batch job. The data import reported that it completed, however it left 12,000 records "Not started". When viewing the batch job, we were able to see that it errored out due to "a temporary problem with the connection to the database." ...
Data Project Import intermitent issue
Giving following error intermittently while importing data project using logicApp. Error Message: XML is not in correct format-Exception from HRESULT: 0xC0010009 '0' 'Bill of materials lines V2' record(s) inserted in staging If we tried to import again it is working. So the error is occurrin...
PO status not updating correctly in when records are created in CE using Dual write
The customer is using the OOTB mapping and also the custom fields mapping but neither of them works for the Live sync: 1. For the current scenario they are using the below for PO status field(Enum Field ): 2. Only when they modify other fields in f&o(address field on the same PO) it updates the...
Ability to apply a limit for integrations (Odata requests)
Currently we are able to add a priority for our integrations in: System administration/Setup/Throttling priority mapping. however it would be useful as well to apply a limit of concurrent requests. We unfortunately experienced an incident that overloaded D365 due to too many requests.
Indexes in the staging tables without system fields
In the staging table the indexes should be created without system fields (e.g. Partition ID, Data Area ID) -> Then we will be able to identify deleted records on the basis of the technical key in the BYODB.
Enforce EDT on the Import of data
In several places in the UI, EDT is enforced so that data is consist. Unfortunately we found out that in some cases the data that flows thru the DM, this data is not bound by that EDT. This means that values that can not been seen in the UI are being brought into the table. Once example is th...
Thanks for the ask. We are in the process of reviewing.
Administrator
Concurrent exports for the same entity to the BOYD database may cause high DTU usage and can result in data loss for incremental exports. To avoid this risk, starting in version 10.0.16, all execution across companies will be sequential per company. This means that jobs with a high number of entities and companies take longer to run.
To reduce the overall export times, consider the following:
Bring your own database (BYOD) - Finance & Operations | Dynamics 365 | Microsoft Docs