I believe that the standard engine may be picking up for integration also records created in tables setup for integration that are used in pages as temporary records.
I will have to test this further, but if you add custom tables in the integration, I believe it won't filter out temporary records in the integration.
If I am correct this must be tested in the standard integration engine.
Comments
I checked the code and I believe the check for temporary records should sit in codeunit 5345 under function SyncRecord.
As you can see in the checks from this function (that looks if a record should be synced or not), there is no check for temporary records.
As the standard integration can be enabled in any environment worldwide (where any of the standard integrated tables can be declared as temporary in any apps or PTE extensions), I think this could cause some serios data issues in the destination systems (Dataverse and CRM).
Solution: A check needs to be added after the line that checks if the sync action is insert or modify.
The check should verify that the source record is not temporary, if it is, then it has to not insert or modify the destination record.
Category: Data Migrations
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team