Filter Data for a Set of Dependent Layouts

You can use all the search options described in Configure Search Options for Download to determine the rows downloaded for the primary layout. The add-in downloads all the children and other descendant rows for the row or rows in the primary layout.

If you would like to further restrict the children or descendant rows downloaded for a given dependent layout, you can define one or more download parameters in that layout.

Take our example of a hierarchy where purchaseOrders is the parent, lines is the child, and schedules is the grandchild. In this scenario, you may have a Form-over-Table layout as the primary layout with purchaseOrders in the form and lines in the table. You also then have a subordinate Table layout for your schedules business object.

To show a single purchase order in the form, you would configure a search in the Layout Designer that prompts the user to enter an order number like this:



Without any other download parameters, Oracle Visual Builder Add-in for Excel populates the form with the user-provided purchase order, and the two tables with all available lines and schedules associated with this purchase order.

To limit the lines and schedules, you can configure one or more download parameters on each table using the Layout Designer. For example, to show all schedules with the same transaction business category, create a search parameter for the schedules Table layout, such as q=TransactionBusinessCategoryId=100. On download, the add-in returns all schedules with the same transaction business category (in this case, with an ID of "100").



This example produces a set of GET requests like this:

/purchaseOrders/{purchaseOrders_Id}/child/lines/{purchaseOrders_lines_Id}/child/schedules?q=TransactionBusinessCategoryId=100

The add-in manages the path parameters automatically.

Note:

Some download parameters may not produce the desired result on dependent layout download. For example, using a "order by" parameter will not work as expected since the add-in sends multiple separate requests for child resources. Parameters such as "order by" should not be used.

Refer to Use the Search Editor to Find Required Data and Use Download Parameters to Limit Downloaded Data.