update references of a loopup property when converting from VL to OT

Hi,

I have a loopup property of a value list. This property is references in many excel files.
Now I have to convert the value list to a object type.
So, there will be a new loopup property for the object type. Due to that I have to replaced the references in the excel files with the new property, so that I have still the values in the excel files.

Is there a common way to do that?

My thoughts are that I create the OT (and take over the data) and after that I delete the loopup property of the value list and use that UID to replace the UID in the new created loopup property of the object type. So, I don't need to replace the references in all excel files.
Is this technically a stable way, or are there unwanted side effects?

Parents
  • Hi Philipp,

    If I remember correctly your lookup property will not change if you simply convert the value list to object type. I think a new property will be added during the conversion process, but the original property will still work. You may need to rename the new one to avoid confusion. But you should not have to change the content of your excel files.

    Please test before you go ahead and do this in production!

    BR, Karl

  • Hi Karl,
    Thanks for the reply. Yes, you are right so far.
    The excel files will be copied and used for new Objects. So the references will be also used with the new property.
    I could still use the old property, but the old prop (from the value list) will not be updated automatically with the value of the new one. ok, that's not a big thing, it can be managed. The other thing is that in the treeview will be displayed boths properties as nodes instead of one. This is confusing for the user and I want to avoid it. Any Idea?

Reply
  • Hi Karl,
    Thanks for the reply. Yes, you are right so far.
    The excel files will be copied and used for new Objects. So the references will be also used with the new property.
    I could still use the old property, but the old prop (from the value list) will not be updated automatically with the value of the new one. ok, that's not a big thing, it can be managed. The other thing is that in the treeview will be displayed boths properties as nodes instead of one. This is confusing for the user and I want to avoid it. Any Idea?

Children