the best way to cook DATs in this case

I have a DAT containing a cell = $cTOP/MASTERS
which I then pass through an eval - cTOP happens to be the path variable of the parent component.
I’ve renamed the parent component, but the DAT didn’t recook, so my ops looking at it are still getting the wrong $cTOP

obviously I don’t want to force cooking at every frame just in case I change some variables.
Is there a way to get the eval to recook? the Monitor data dependencies is checked, but maybe doesn’t apply in this case?
I have output as “strings” - because “expressions” outputs a 0 instead of the /MASTERS

tx

There is currently a deficiency in our monitoring code that whereas the notification that goes out when a node is renamed (causing things to recook), doesn’t go out when one of it’s parents (parent, grandparent etc.) is renamed. Often it’s just as important that a node’s parent was renamed as if it was renamed, since it’s absolute path has changed.
its on the bug list, not sure what the best workaround is right now though.

here’s a workaround.

keep the eval DAT output parameter at strings and use opfullpath("$cTOP")/MASTERS in your cell. Should update fine