Add custom column dependency via DialogNotification

Question

Using $ notation we can establish dependency between objects if target object has foreign key that points to source object. E.g. in ADSAccount.samaccountname we can use FK(UID_Person).centralaccount. And it works great. But what if foreign key points in another direction. E.g. we want to populate Person.customproperty01 based on ADSAccount.ExtensionAttribute1. Of course there are standard ways to do it: via process or 'on saving' script www.oneidentity.com/.../triggering-a-template-by-changing-a-value-in-another-table 
 But I wonder if it is allowed to add custom entry to DialogNotification table. The table looks very generic, so recalculation should work (and in Person.customproperty01 I will calculate desired value with script). Or this table should not be modified manually?

Markus Weiss-Ehlers · Answer

Do not modify the entries in DialogNotification manually. They will be updated by the database compilation.

Markus Weiss-Ehlers · Answer

First, the notification entries just control the need to execute a template. But even if the notification entries would be there, the EntityWalker (or ObjectWalker) wouldn't know how to identify the "Assigned" ADSAccount entry, hence you wouldn't be able to update the property correctly (or easily). 
 Secondly, in contrast to the case with the foreign key you would have to deal with n potential candidates, and you do not know explicitly what columns need to match. Just because in your example the PK UID_Person matches the child property UID_Person (in ADSAccount) by name, doesn't mean it always has to be the case. 
 That's why you can use the OnSaving (or OnSaved) script to solve your use-case.