No we’re going to import some IndustraForm data. We’ll start by importing data entered in to previous handovers for Unit 1 so that we can show a trend of our KPIs.
Again, we add in the layout first, as in the diagram above. This time we will use the following formula for the Data Binding:
"shift_date,shift,AAPRTarget,AAPR,ACPRTarget,ACPR,CSTLTarget,CSTL"), "shift_date>=?", TODAY()-
The IMPORT.LOG function, like the IMPORT.MYSUBLOG function, will import data from a set of logbook entries. However, as this example demonstrates, these functions can also be used to import data from the IndustraForms that are attached to them.
IndustraForm element names can be included in the list of requested columns. In this case, only rows that contain an IndustraForm that has all of the required elements are returned. It is possible to indicate that a particular element is optional, however, by adding <ElementName>.IsDefined to the column list.
We are using the IMPORT.LOG function for this example, because the data we are looking for is not available in a sublogbook of the Handover entry. As we mentioned earlier, the IMPORT.MYSUBLOG function applies some useful filters automatically. When using the IMPORT.LOG function, however, we need to specify the appropriate filters ourselves.
That is were the FILTER function comes in. This function will apply an SQL-style filter clause (the second parameter), to an imported table (the first parameter). And further parameters to the function will be substituted for question marks in the filter clause, in the same order as they appear.
A later chapter will discuss filters in more detail, but our filter for this example will only include entries from the previous week:
=FILTER(<Table>, "shift_date>=?", TODAY()-7)
In the following chapter, we will show how to display this trend information in a chart, instead of a table.
See the IndustraForm YML file here: Step 6.