I have a composition called _Person Base that is used in 1 Data Type (Person) and a Document Type. Let's call it Presenter.
The problem is that _Person Base has more fields than Presenter needs. I've been asked to remove the extra properties so Content Editors are not confused. The Person Data Type should remain the same.
I don't want to lose content already entered.
I created a new composition that duplicated the properties on the original _Person Base using the same alias names for the properties. From an initial test, it looks like entered data does not get lost for Presenters.
I want to confirm that this is an ok practice. What should I look for? Am I setting myself up for trouble?
I have had this experience with compositions as well.
As long as you remove the composition from a Document Type and before saving you add your properties back in with the same aliasName the data will not be lost behind the scenes.
Obviously backup your database before testing this however I am 99.9% sure your data will not be lost.
Duplicate property aliases on different compositions
v13.3 Cloud
I have a composition called _Person Base that is used in 1 Data Type (Person) and a Document Type. Let's call it Presenter.
The problem is that _Person Base has more fields than Presenter needs. I've been asked to remove the extra properties so Content Editors are not confused. The Person Data Type should remain the same.
I don't want to lose content already entered.
I created a new composition that duplicated the properties on the original _Person Base using the same alias names for the properties. From an initial test, it looks like entered data does not get lost for Presenters.
I want to confirm that this is an ok practice. What should I look for? Am I setting myself up for trouble?
Hi Donna,
I have had this experience with compositions as well.
As long as you remove the composition from a Document Type and before saving you add your properties back in with the same aliasName the data will not be lost behind the scenes.
Obviously backup your database before testing this however I am 99.9% sure your data will not be lost.
Cheers,
Marc
is working on a reply...