+2
We get validation error messages for default Thinkwise validations that are actually deprecated:
(It also throws an error while navigating to related object)
How can we prevent that deprecated validations are ignored during validation?
Best answer by Jeroen van den Belt
View original
+8
Hi Dave,
Possibly, your model is using a base model which still contains these obsolete validations. You can check if this is the case, and first generate that base model (which should clear the obsolete validations there) before regenerating your work model. For more information, see the part regarding nested base models:
https://docs.thinkwisesoftware.com/blog/2024_1#re-generate-model-definition
Does this help?
+2
Yes, thank you Jeroen! My custom base model still had some obsolete linked base models it self. After they were removed and generation the validations were gone.
Is it an idea to create a default Thinkwise validation (for workmodels) that check when a nested base model is actually duplicate?
And still, shouldn’t deprecated validations be ignored by the validator?
+8
Our product development team actually has a user story that focuses on the situation of outdated base data in base models. I don't think we'll go for the validation to detect this, but even better, a solution to prevent this.
The story is not planned yet, so if this is really important to you, you could create an idea in our ideation section in order to try speed things up.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
