Hi all
Hoping someone can help me with the following: If a child asset has a value directly applied to a certain metadata field, is there any way to avoid that being overwritten (by default) when the same field is updated and cascaded from a parent asset?
I hope that makes sense and cheers for any wisdom.
Hmm, don't think so, unless you use something like workflow and the person cascading the value from the top doesn't have direct workflow approval to make changes straight away. Bit overkill if you just need it for 1 asset though. What's the use case?
One example would be:
Changing a Parent’s ‘page-owner’ metadata as per below structure.
Ideally we’d want the Parent’s new value to cascade only to descendants with metadata of the same value ‘ContactX’:
e,g:
Parent (page-owner metadata = ContactX)
|
Child page (page-owner metadata = ContactX)
|
Child page (page-owner metadata = ContactY)
|
Child page (page-owner metadata = ContactZ)
Disabling metadata cascade would require many pages of manual metadata updating.
Hmm, ok, so if I then change Parent’s page-owner metadata from ContactX to ContactA,
it would also change the value of Child Page that has page-owner metadata ContactX to ContactA
?
If that’s the case you might be better off using a trigger perhaps?
Yes my dilemma, Trying to keep unique child metadata pure from cascades.
Cheers, I will look into triggers.