Ahmed Gamal

When the username in M365 is changed through a UPN change in Azure, the new username is able to sign in to the D365 F&O environment with the new user. However, the new user is not automatically updated in the system administration users page and a manual username change is required from the old user (which becomes an alias) to the new user (which becomes the main user).

This causes issues with changing user options in F&O because the username is not synced automatically to F&O while the Azure security feature is not enabled for this environment.

The standard Vendors V2 (vendors) standard mapping has the below fields for the On hold status:

no, invoice, all, payment , requisition and never

while the vendors table itself has one more standard field called purchase order as showing below:

The purchase order field if used we get the below error:

Error is Unable to write data to entity msdyn_vendors.Writes to VendVendorV2Entity failed with error message Request failed with status code BadRequest and CDS error code : 0x80048d19

we can solve this by manually adding the purchase mapping value to the dualwrite which means we need to customize every time creating this mapping.

we are asking to change the standard dualwrite mapping by adding the value purchase order to the ONHOLDSTATUS mapping field for them not to face this in future implementation mentioned here:

Rounding is not working while publishing purchase agreement line via excel add-in or DIXF import with decimals 

the rounding that is set on the unit decimal precision of quantity in the purchase agreement is only working when adding the number from the F&O UI.

we need to have this controlled to be rounded through excel or through F&O according to the field that has the rounding decimal possessions set.

 Issue:

  Our team has experienced multiple pauses in the "CustInvoiceLine" table syncing process due to large data (570 million of records) and missing indexes and throttling while syncing a large volume of records. This issue arises because the current Tier 2 sandbox lacks the necessary resources to handle these large sync operations efficiently. Conversely, the production environment completes these sync operations promptly.

 Proposed Solution:

  We propose upgrading the sandbox environment to a higher tier with more resources to facilitate more efficient data synchronization. Additionally, allocating more resources within the sandbox specifically for data synchronization, similar to the efficiency observed with exporting to the data lake, would greatly improve performance.

 Benefit:

  This enhancement will reduce errors and retries, ensure smoother and quicker data syncing, and maximize productivity by mitigating sandbox limitations.