Disappearing translations from base model

Hi ​@Mark Jongeling!

Thanks for your response, I was looking over what you said and investigated a bit, seems like the English translations are there because a base model (which is having the english translations) is attached to this base model. This base model indeed contains only translations and what else is attached by the mentioned base model with english translation.

I have tried to run the script you mentioned and got 

Msg 547, Level 16, State 0, Procedure task_import_model, Line 55549 [Batch Start Line 0]
The DELETE statement conflicted with the REFERENCE constraint "ref_col_col_data_sensitivity"

But this may be because of attached base model. 

I will check with the team if we really need it to be for this translations base.

This is caused by Data sensitivity. Someone probably has configured that for this base model, or it got imported via the attached base model. It's really strange you get this as the SQLSERVER_MSG_TRANSL_NL does not contain any columns, so something truly went wrong….

At this point it's difficult for me to determine what way to resolve this issues.

The SQLSERVER_MSG_TRANSL_NL should not have any base models attached. Disconnect any that are attached. Run a Definition generation to remove any leftover generated objects. At this point, the model should only have Messages, Translation objects, and Translations. If not, remove the objects that should not be part of this model, especially Tables and Columns.

Hi,

We have similar problems with SQL base model translation constantly returning. Have not figured it out, and also in TEC they couldn't explain it. If you find a solution, please let us know! 

Blommetje

Probably the best way is to create a ticket in TCP. I think we'll need to call to resolve this effectively.

Hi ​@Mark Jongeling!

We discussed internally and concluded that is better to leave the base models Thinkwise provides without our touch over them.

We removed the base models that were attached to base models from Thinkwise, and for this specific case we were able to apply the script you pointed out and looks ok now.

​@Blommetje about the messages that you pointed out, I think we also had them and we just searched for the root base of those and translated them and they dissapeared, if you already did that, I'm not sure what else to suggest.

Awesome!, it is indeed better to leave the Thinkwise base models the way they are distributed. Otherwise all kinds of errors may occur during platform upgrades as we do expect the base models to be exactly as we distribute them. We do intend to make these models "Read-only” for everyone at some point. If you do want to add or modify certain parts, you can opt to create a branch off the MAIN branch. 

In that branch you can perform the desired modifications and link those to your models. Only the MAIN branches of the Thinkwise distributed base models are updated every platform upgrade. This does mean if you go this route, that every platform upgrade, you will have to update your branch from the MAIN.