Recommendation - use master detail relationships when authoring decks

Decks offer greater flexibility in active reports by allowing you to show different objects in each card of a deck. In data decks, the number of cards that are created depends on data items inserted in the deck. As a result, a data deck can contain many cards, which may reduce performance when the report is run and viewed. For example, if a data deck contains Product line and Years, there can be up to 20 cards in the deck (five different product lines multiplied by four different years). In addition, filtering data in a data deck can affect performance when there are many rows of data in the deck.

To improve performance, use a master detail relationship to filter data in a data container inserted in a data deck control. A master detail relationship defined between a data deck and a data container inserted in the deck results in a specific number of cards generated for the deck, which serves as a way to filter the data in the data container. For example, a data deck contains a list object that has many rows of data, and you want to filter the list by product line. Creating a master detail relationship between the deck and the list using Product line produces five cards in the deck, one for each product line. When you filter by product line, the appropriate card appears in the data deck.

In addition, specify Select as the behavior instead of Filter when defining the connection between the data deck control and the control you want to use to filter the data in the deck.