It is very annoying when a model import fails because of invalid characters in the model.
I did a invalid XML character test, but pipe symbols in Screen Type ID's were not detected. Errors also occurred for Runtime Configuration ID's with brackets in it.
It would be better to enforce a proper validation in the model export routine.
Hi Harm,
While we agree that addressing this is a good idea, we’d like to propose a slightly different approach. Although the issue becomes apparent during model export/import, its root cause lies in the data within the model itself. Ideally, this is something you’d want to validate at any time, not just during export/import. This is an idea that can be further developed—let’s open it up for votes.
Hi Jeroen,
You are right! We need to be able to trust the content of the model at all times. Validation screen can help with that, but even better to apply as many validations as possible in real time, during modeling.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.