We are currently using Project Operations, D365 F&SCM, and Dual Write. At the moment, we are facing synchronization issues with msdyn_actuals, which is showing the following error message:
Reason: Bad Request, Header x-ms-client-request-id f898b757-b2e9-4329-94c0-edce69d760ce, Kenmerk msdyn_transactiontypecode niet gevonden in de record van het type msdyn_actual.
Additionally, msdyn_transactionconnections is encountering a different issue that might be related:
[DIPV1030] Data type mismatch - [msdyn_transactionconnections.msdyn_transaction1(Transactie 1)] is of [String] type while [Integration entity for project transaction
relationships.TRANSACTION1ID(TRANSACTION1ID)] is of [Guid] type; this can result in errors or data loss if the contents exceed or violate data type restrictions. [Guid] is more restrictive than [String].
[DIPV1030] Data type mismatch - [msdyn_transactionconnections.msdyn_transaction2(Transactie 2)] is of [String] type while [Integration entity for project transaction relationships.TRANSACTION2ID(TRANSACTION2ID)] is of [Guid] type; this can result in errors or data loss if the contents exceed or violate data type restrictions. [Guid] is more restrictive than [String].
Right now, we are unsure whether these two issues are connected or how to resolve them.
Resolution:
I suggested this Microsoft documentation to the cx
https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/dual-write/customizing-mappings#customize-column-mappings-add-transforms-and-enable-filtering
After That
Customer Said
The error message indeed clearly points to a data type mismatch, and we understand that the solution likely involves aligning the data types.
The challenge, however, is figuring out how to do this given the complexity of the msdyn_transactionconnection table and what best practices recommend in such cases.
When reviewing the transaction1 and transaction2 column properties in the Dataverse msdyn_transactionconnection table, it appears that changing the data type from string to lookup (GUID) is not possible.
The error message indeed clearly points to a data type mismatch, and we understand that the solution likely involves aligning the data types.
The challenge, however, is figuring out how to do this given the complexity of the msdyn_transactionconnection table and what best practices recommend in such cases.
When reviewing the transaction1 and transaction2 column properties in the Dataverse msdyn_transactionconnection table, it appears that changing the data type from string to lookup (GUID) is not possible.
AS they are using OUT-OF-BOX Field So it is not possible to modify these fields, so they have some concerns regarding this:
If creating new columns is considered best practice, how should we configure them given the complexity of the data in the msdyn_transactionconnection table?
For instance, since the unique identifiers seem to originate from different tables such as msdyn_actuals or msdyn_journalline, which related table should we choose for the new transaction1 and transaction2 columns to ensure data consistency?
Share
Report
All responses (
Answers (
41
