Does changing Lookup to No for existing Reference attributes cause issues?

[LisaParticipant]

Hey,

when changing the selection for “Lookup” to “No” for an existing Reference attribute of an entity type, is the previous lookup entity selection saved, after changing “Lookup” to “No”?

Could this cause any issues during the deployment via Marketplace?

Kind regards,
Lisa

[kathyParticipant]

Hi,

when changing the selection for “Lookup” to “No” for an existing Reference attribute of an entity type, the previously selected lookup entity type remains saved.
Changing the datatype of an attribute can cause issue within the data that had already been saved.
Before changing the datatype of an attribute, please consider that this might lead to issues or complications, such as e.g.:
– the data of the affected attribute may no longer be displayed correctly
– some data may get truncated, in case the previous datatype allowed to save more characters
– some reports and displays (e.g. Data Explorers) may no longer properly work
E.g. Changing a “short string” to an “integer” may not work, as an integer contains only numbers while a short string can contain letters and symbols as well.
However, changing an “integer” to a “short string” should be fine, as the characters saved for the integer can easily be saved as text as well.

Why do you want to change your attribute?

Best wishes

• This reply was modified 1 year, 5 months ago by kathy.
• This reply was modified 1 year, 5 months ago by kathy.

[Author]

Posts