datasource linked clones

Locked

Discussion interactions are currently paused.

I have noticed that a common pattern with LM is to clone a datasource and tweak it, mainly for the Applies To. Each time this happens, if an underlying change is found to be needed, this must now be replicated into every clone, offering many chances for semantic divergence over time. How about adding the idea of a linked clone, so that all clone fields are tied to the original DS until overridden? The applies to can be overridden by default, as is done now, but then you can benefit from changes to the original DS in the clones except for any specific changes made to them via override.

Thanks,

Mark

mnagel

Posted 10 years ago·Last reply 10 years ago

1 comment

Josh_Selinger

·10 years ago

Interested!

1	SUYASH GAIKWAD
2	PJ Pankaj Jain
3	KT Kyle Taylor
4	KV karthikeyan VG
5	ME Mir Ehtesham Ali
6	SN Sangeetha Nataraj