GUI Script - Header Detail

Following are the various mapping types supported in GUI Scripting module:

  • Where you know that number of detail rows is always fix, say 4 rows.

    GUI_Script_Header_Detail_1

    Mapping is as displayed in the following screenshot.

    GUI_Script_Header_Detail_2

  • Process Runner automatically determines new transaction when value changes. For example, you have Document number repeated for each line in column E, You can use this mapping type and every time there is new Document number, Process Runner will start a new Header-Detail transaction automatically.

    GUI_Script_Header_Detail_3

    Mapping is as displayed in the following screenshot.

    GUI_Script_Header_Detail_4

  • This option is the same as the On Change option, but instead of repeating Document number, you have blanks between Document numbers. Since a blank is a change, you want to tell Process Runner to ignore blank for considering them as a change.  With this mapping type, Process Runner will ignore those blank and will repeated new Header-Detail transaction when it encounters new Document number in column E.

    GUI_Script_Header_Detail_5

    Mapping is as displayed in the following screenshot.

    GUI_Script_Header_Detail_6

  • For example, you are separating Header-Detail block by placing a blank line between each block of Header-Detail transaction. You can use this mapping type and anytime Process Runner encounters a Blank Cell in mapped column, it will automatically start new Header-Detail transaction.

    GUI_Script_Header_Detail_7

    Mapping is as displayed in the following screenshot.

    GUI_Script_Header_Detail_8

  • Same as the On Change Ignore Blank option, but instead of changing value, it always starts a new transaction when it finds a value in the column whether it’s same or different. It will ignore blank. In the following example it will consider line 6 as new header-detail transaction even though the document header text is similar to previous one.

    GUI_Script_Header_Detail_9

    Mapping is as displayed in the following screenshot.

    GUI_Script_Header_Detail_10

  • Additionally to above mentioned methods, you can also specify which rows to be used as header and which to use as a detail in a separate column. As shown below, Headers are named as H and detail as D. You can give any user defined names to header-detail items instead of just H and D.

    GUI_Script_Header_Detail_11

    In the following screenshot of the mapper, K indicates the Legacy loop column H and D indicate Header and detail items.

    GUI_Script_Header_Detail_12

Note:

  • There are two fields to map for Header-Detail looping - one is Block Type and another is Block Value. These two fields are over and above regular mapping fields. These fields are used together to tell Process Runner how data in Excel file is arranged.
  • You maintain Block Type and Block Value in the same row as the Start Loop.

When you set loops to upload multiple line items information, you can map Excel Column Index (column name) or Excel Column Header text (Excel header cell) in the Block Value column. For information about mapping Excel header Cell, see Map Excel Header. Note that this feature does not support to loop when Block Type is set to Fix Block.