Skip to main content

Hello,

 

I m curently working on a model that would become a base model for some of the work models. Yet, the base model would require adjustments and future development later on. The base model contains functionalities that ar linked to work model procedures and so, means that the work model depends on the base model. 

So far I descovered that any small changes in the base model would impact any other model that contains the base model, even if the changes are for testing purposes or part of development.

That means if the base model is already in production or development environment any new branch created from those would be affected by any changes from the base model.

How can I work with that as a best practice, considering that I cannot unlink the base model from the work model?

 

Thanks,

Paul

Hi ​@TurcuPaulAndrei,

How we ourselves do it is keeping the MAIN branch as the branch that toher work models will use. If anything needs to be added/modyfied/removed, we make a branch of MAIN, do the work and merge it back when the time is right. This does indeed impact the work models in a way, but I think with careful planning the impact can be kept to a minimum.

So in essence, you can work in base models the same way as in work models.

Hi,

 

But how I can test what I change if i cannot change the base model to work model?

You can actually 😄 in Model overview > Branches > Base models, you can ee the list of base models tha are and aren't linked to your branch. With the Update branch task, you can change which branch is linked.

Update branch task

When selected, you can choose which branch should be linked instead.

 

Sidenote; By default, the Base models screen shows the last inserted branch (if you did not link the model yet)

Reply


Terms & ConditionsCookie settings