en:renameissue
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
— | en:renameissue [2021/03/25 13:09] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | TitleEngTAG | ||
+ | |||
+ | |||
+ | |||
+ | < | ||
+ | |||
+ | For the RENAME operation it was observed a singular behavior to be careful of, while we are studying a specific solution. | ||
+ | |||
+ | **Referential integrity management in case of RENAME** | ||
+ | |||
+ | The RENAME management is particular, since Dynamics 365 Business Central apply the referential integrity management operations defined in the database, in addition to standard OnRename trigger code: for example, when the user apply a RENAME on a [Customer] record (changing its primary key), the same modfication is applied by Dynamics 365 Business Central also to the referencing fields of [Sales Header], [Sales Invoice Header] and so on (Sell-to Customer No. etc.) | ||
+ | |||
+ | Unfortunately, | ||
+ | |||
+ | In case of RENAME + MODIFY: the target system receives a report of RENAME and replicate it directly, automatically triggering the local referential integrity management system; the next MODIFY transaction will be considered an unnecessary step, not creating a real problem nor error logs. | ||
+ | |||
+ | In case of RENAME + RENAME: the problem arises when the modified field is referenced by a key. Let you think for example to have both the [Customer] table and the [Customer Bank Account] table set for replication: | ||
+ | |||
+ | Sprinkler will report both the RENAME of the Customer and the RENAME of a corresponding record of the [Customer Bank Account]. The second operation, however, will find the record __already renamed__ directly by the target Dynamics 365 Business Central referential integrity management system, so Sprinkler will raise a false positive error. This error (starting from v.0.5.00) is managed and reported in the [Data Distrib. Import Error] table because the record to be renamed does not exist anymore, but this behavior can be difficult to be recognized and understood. | ||
en/renameissue.txt · Last modified: 2021/03/25 13:09 by 127.0.0.1