https://communities.bentley.com/products/geotechnical1/f/geotechnical-forum/174551/gint-rules-and-data-importHi there. We have a system where there are several gINT rules in the database used for validation. I&#39;ve noticed that you can import data which can break the validation rules and it isn&#39;t picked up until you actually open one of the tables where thereen-USTelligent Community 12https://communities.bentley.com/thread/504059?ContentTypeID=1Fri, 01 Feb 2019 23:46:32 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:9c4e69b4-feed-43c1-a0b3-c17945ad84c6Kirk Johnson<p>Hi Paul,</p> <p></p> <p>Yes that is correct. It is by design. I did verify with our development team.</p> <p></p> <p>The way it works is gINT imports the data into a table so it can validate it with gINT Rules.</p> <p></p> <p>The import log will provide information about the checks.</p> <p></p> <p><img alt=" " src="/resized-image/__size/320x240/__key/communityserver-discussions-components-files/283906/check.png" /></p> <p></p> <p>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.</p><div style="clear:both;"></div>https://communities.bentley.com/thread/503957?ContentTypeID=1Fri, 01 Feb 2019 08:56:41 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:30f16fda-4e5b-4ddd-adc3-3b2300d9aac8Paul Chaplin<p>Obviously I know that a log file can pick up these errors, but I don&#39;t think it always stops the data going in.&nbsp; It will highlight warnings of things that aren&#39;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&#39;t been imported.</p><div style="clear:both;"></div>