We recently discovered a limitation within dual-write connected with opened transactions. When transaction is opened and within it e.g. invoice header and invoice line is created the line rises an exception if it has an reference in dataverse to invoice id from the header. It's because DW logic is executed before actual commit, so the header is not yet in the DB. When there is no transaction(s) involved it works as it should. Is there any way to fix it on Dataverse level while keeping the reference or the transactions will have to be reviewed and changed?
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.