Hi
Recently we faced below issue in one of our environment
1. We renamed one of our rule , on dev environment this rule was referred by 10 other objects. all the 10 objects got updated to reflect the new child name
2. When we deployed the renamed rule on target environment . out of 10 only 7 objects got updated .
3. Also remaining 3 objects were also not coming in the dependent list of renamed rule. but they are suing the renamed rule
Does any one faced the same scenario. Also my understanding is when rename the rule upon deployment all the referenced object should be updated there is no special scenario when it does not gets updated (except some one has opened the rule in designer )
Thanks
Ajinkya
Discussion posts and replies are publicly visible
Right after the ability to rename rules was introduced, I noticed a similar issue particularly when renaming very old expression or query rules (4 or 5 years old). I opened a support case for it but never confirmed whether the issue had been identified or fixed exactly. In the cases where I was able to reproduce it, I had similar failures on different environments when attempting the rename, but I can't speak for how it'll always behave.
In general when renaming legacy objects, I recommend collecting all dependents of that object into an app package to spot check afterwards and/or do a "by expression" search against the old object name to verify that no instances of the old name are still in use.
Please open a support case for this so that the product team can be made aware of the issue.