Transport and ScopeReferenceColumns

Does anybody know how to stop the VI.Common.Customizer.DialogTable from checking the ScopeReferenceColumns when transporting schema extensions? It becomes a chicken / egg situation, the scope is defined on the table but the referenced column is not transported yet. The column is transported later in the same transport file. The transport will fail with a message: 'Table CCC_Table does not have column CCC_UID_Reference.'. It seems an error to me if we have to:

  • Remove the scope from the tables having a scope reference.
  • Transport the schema extensions
  • Add the scope to the tables
  • Transport the changes

Is there a way to disable this check that does not require a SQL delete and later insert statement?

Parents
  • In similar cases we usually we split all into several transport files.. The column extension comes first, then comes the reference. 
    Personally, I don't think that blocking the customizer check is a good idea. 

    P.S. I'm very sorry about the typo in my question post.

  • Hi Sargay,

    The customizer must not run the check while the transporter is importing schema extensions. It is not normal that you have to change your working and necessary configuration just to be able to transport the changes to another database? The error message also does not excel in pointing out the issue. I will create a support issue for this. 

Reply
  • Hi Sargay,

    The customizer must not run the check while the transporter is importing schema extensions. It is not normal that you have to change your working and necessary configuration just to be able to transport the changes to another database? The error message also does not excel in pointing out the issue. I will create a support issue for this. 

Children
No Data