Documentation

Storing building blocks within other building blocks

Building blocks can be stored in the database directly, in which case they have a name and are visible in the Building Blocks window. Or they can be stored within other building blocks. In the latter case, they are not named and are not visible in the Building Blocks window.

Common reasons for storing inside another building block include:

  • Lists that are nested in lists (master/detail) are best stored in the containing list, especially if the nested list has no use outside its containing list.

  • Data sources that are used only for one list or graph can be created within that list or graph and therefore will be stored within it.

If you find the need to re-use a building block that is hidden inside another building block, you can change the storage. Example: Suppose you have a list "sales1" that contains a nested list for showing the sales' line items. In this case the nested list is stored inside "sales1" and it has no name. Now, you want to create "sales2" which has a different format to show sales, but you can use the same format for the line items. Go to "sales1" and select the cell that contains the nested list, and choose Nest/Link Properties. Press Change Link, and answer the questions as appropriate to save the contained building block with a name. Once this is done, the line-item list will be shown on the Building Blocks window with a name, such as "sale line items." The list "sale1" will now reference "sale line items". You can now create "sales2" and re-use "sale line items" as a nested list.

(c) 2014-2015 Divergent Labs, Inc.