Log configuration instance reference
I have an Log Configuration Aspect im my Object. The aspect in not inherited, it is "copy to all aspect" that's ok.
But now in some instances a disabled and enabled the checkpox "Enable" due to some log problems. After this this change I lost the reference to its object. Changes in the Log Configurtion of the object have now no impact to this instance. Ho can I reconnect this instance to its object again.
But now in some instances a disabled and enabled the checkpox "Enable" due to some log problems. After this this change I lost the reference to its object. Changes in the Log Configurtion of the object have now no impact to this instance. Ho can I reconnect this instance to its object again.
Asked 1 month ago
Answers
0
This is the negative side of using "Copy to all instances" (also known as Auto-Instantiate).
I have written many times here on AKS about the caveats of using this method to "fake inherit" aspects from type level down to instance level. What looks so promising in the beginning often becomes a nightmare in the end.
If you want inheritance back, you need to start from scratch since you cannot delete any aspect on instance level as long as the auto-instantiation is enabled. Resetting the flag will remove aspects from unchanged instances only while they remain(!) on changed instances, so before turning the flag on again you must manually purge lingering aspects to avoid having duplicates in the end. This may seem like bollocks, but is the naked truth.
Instead of wasting time and efforts on this over and over again I sincerely recommend to use bulk tools (two exists for Log Configurations, a) Bulk Data Manager and b) IM Bulk sheet) to "Xerox" the present log configuration, after which you wipe them and then recreate them using the bulk tool, not auto-instantiate.
Data will go lost, but may be salvaged using backup tools (have you read about the AdvHtArchiveTool.exe part of online upgrade?) - I believe it may work as long as the object GUIDs remain intact hoping it can accept new GUIDs for the log configuration aspects.
I have written many times here on AKS about the caveats of using this method to "fake inherit" aspects from type level down to instance level. What looks so promising in the beginning often becomes a nightmare in the end.
If you want inheritance back, you need to start from scratch since you cannot delete any aspect on instance level as long as the auto-instantiation is enabled. Resetting the flag will remove aspects from unchanged instances only while they remain(!) on changed instances, so before turning the flag on again you must manually purge lingering aspects to avoid having duplicates in the end. This may seem like bollocks, but is the naked truth.
Instead of wasting time and efforts on this over and over again I sincerely recommend to use bulk tools (two exists for Log Configurations, a) Bulk Data Manager and b) IM Bulk sheet) to "Xerox" the present log configuration, after which you wipe them and then recreate them using the bulk tool, not auto-instantiate.
Data will go lost, but may be salvaged using backup tools (have you read about the AdvHtArchiveTool.exe part of online upgrade?) - I believe it may work as long as the object GUIDs remain intact hoping it can accept new GUIDs for the log configuration aspects.
Add new comment