• State Not Answered
  • Replies 1 reply
  • Subscribers 95 subscribers
  • Views 466 views
  • Users 0 members are here
Options
Related

Custom attribute transport

Anton Akimov
over 3 years ago

Greetings!


in One Identity Manager 8.1.4 we have created a new attribute using Schema Extension tool in our DEV environment. We did the same on our production environment. The attribute has the same name and type on both env.
Then, during the attribute template transports, implying this attribute (using Data Transport tool) we are getting issues as the object key for the DialogColumn is not the same.
"Object with key <Key><T>DialogColumn</T><P>CCC-8978712EEC5F7242BE333DC42C9250CE</P></Key> does not exist in database"


I know that normally, if an extension has been saved on a Change Label, there is no such problems as the object UID is also replicated during the transport.
Is this the only way to transport custom attributes from one environment to an other?(using change labels)

What would be a workaround in our case? => knowing that the attribute was created separately on both sides.

Best regards,

  • 0 over 3 years ago

    Hi Anton,

    If you create a schema extension in DEV you should NOT create the same schema extension in PROD.  Simply use the transporter tool to transport schema extensions from DEV to PROD .... in doing so the UID's will be preserved.

    Sounds like you will need to delete the schema extension from PROD and do what I have said above.

    HTH, Barry.