Hi there.
We have a system where there are several gINT rules in the database used for validation. I've noticed that you can import data which can break the validation rules and it isn't picked up until you actually open one of the tables where there is invalid data, attempt to change something and swap to another table.
Now, you may have edited a lot of information in that particular table but are unable to commit the changes due to having to exit that table and go to a different table to amend the data that is breaking the validation. Is this by design or is there any way during import for the validation rules to be invoked so that bad data is caught prior to import?
I can see that most of our rules are set on "After Updating Grid", "On Save" and "After Save". Is there something that we may have missed?
Obviously I know that a log file can pick up these errors, but I don't think it always stops the data going in. It will highlight warnings of things that aren't in the library etc but ideally I would like an opportunity to stop the entire dataset going in, rather than pick through the log to find out which bits of data haven't been imported.
Hi Paul,
Yes that is correct. It is by design. I did verify with our development team.
The way it works is gINT imports the data into a table so it can validate it with gINT Rules.
The import log will provide information about the checks.
There is not a feature to precheck data before or during import against gINT rules that are stored in the library and referenced in the project table.