By David Crowther
Question:
Why is the MapThat Report Generator not exporting some records into the final report?
Answer:
The MapThat Report Generator tool allows you to run any number of spatial checks against multiple GIS layers and is perfect for quickly and easily undertaking constraint checking.
Here is a Blog detailing the benefits of this tool - https://www.cadlinecommunity.co.uk/hc/en-us/articles/360018942637-MapThat-Report-Generator-Con29-made-easy-
… and here is an example report output, which can be adapted per Client and per Report type!
However, if the output reports do not include all the expected layer records, then here are some tips to resolve the issue:
1 – Ensure the layer/table being queried does not have any invalid geometry. It is your spatial database that undertakes the spatial analysis using database triggers and if one of your spatial layers has invalid geometry, that spatial analysis can’t be run and so the report won’t be able to show records for that layer/table. Here is an FAQ on invalid database geometry and how to handle it - https://www.cadlinecommunity.co.uk/hc/en-us/articles/115002814585-MapThat-Admin-Geometry-Make-Valid-Error-Message
2 – Make sure that any field to be added into your output report either has values or NULL values in each record. If your database table has BLANK values, then the report will not be able to add results from that table into the output report.
So, for the above table ensure that the Note field is updated with values or at least a NULL value.
3 – If the report still fails to include records from one of your output tables, then its likely that there is a field in the source table that clashes with a field you use in your output template. The Report Generator allows you to add any number of fields from the source tables into the report, as well as other static values e.g. a date, and user defined variables, such as Search Numbers, Address information etc….. So, check if you are using variables named the same as your table field names, and if you are then update your variable names accordingly. For example, below, the source table field is called Search_Number but we will add this to the report by using the template variable SEARCHREF.