IA Report Builder – 1 December 2017 Release Notes

The latest version of Report Builder (v 1.6.14) is out now!

In this version we have fixed a few bugs, added support for filtered layers, allowed re-ordering of indicators on a widget by widget basis and provided more information on the data sources used in your report.

Filtered layers

In some cases you may not want to produce a report for all the features in your map layer.  While you could just direct users to the report for the particular feature the index page would show links to them all.  Report Builder will now recognize any filters set on your layer.  You can set the filter on the layer itself or define it in the webmap.  You can also now connect to datastore if you are basing your report on a filtered layer

Indicator Order

You can now override the order of the indicators in your individual widgets.  Just go into the Data tab of your widget properties and click on the ‘Set indicator aliases for this widget’  From here you’ll be able to move indicators up and down in the list

Web Map Legend

The web map widget now has a setting allowing you to include a legend.


You can now easily embed an iframe into your report.  This can be useful if you want to embed other web pages or apps from elsewhere.  For example, if you want a fully functional map app in your report this could be a good way to do it.  We do this by using the text widget.  Once you’ve added one to your report simply double click on the widget to open the text editor and then go to the source code using the <> in the menu and paste your iframe code in.

Data Source information

If you go to the “Data sources” under Report Settings tab you will see a small “i” beside each data source.  This will provide information on the relevant feature layer; which webmap it is part; csv; data store; arcgis server layer etc.

This was a popular feature request as it can be difficult to remember exactly which webmap / layers you originally built a report from.


  • Fix for Related Records widget in “geographic mode” so that queries can work across feature services with differing coordinate systems