Any thoughts on this?
Thanks Anne for your insight, would be nice to have a future proof solution for this. I created an idea
We did some testing regarding this issue:we changed the base model to a non-base model the model which was using the original base model still loads the functionality from this now non-base modelThis helps us in the way we set up our projects/models, because we can now run and test our non-base models seperately with the option to still load them into other projects/models.But if you guys consider this as a bug, we might lose this workaround.Our suggestions when you decide this is a bug:Could work models also be considered base models for other models? Could we mark a branches as work/base model?What is your opinion on this?
Thanks Mark,I made a ticket in TCP.We could easily bypass the bug, because we have one domain for all map data objects. I changed the <UPGRADE> update in dom_id, by putting in our domain name in the script. The rest of the upgrade went smoothly.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
