Data Source & Join

<< Click to Display Table of Contents >>

Navigation:  Report Builder >

Data Source & Join

Previous pageReturn to chapter overviewNext page

Component Data Source

 

Data components such as the MeasureBox, Chart, Table, and List can have their own data source, this data source is referred to as the component data source. This data source is individually queried from the data connection then applied to the component. Each component using component data source can choose to join the report data source by using a selected key from both ends. Without any data join, the component will be displayed independently. If the component is placed in a Group Header, it will be repeatedly displayed along with each group value, since join is undefined, it will display the same value(s) in every group value. If the component is placed in the Detail section, it will be repeatedly displayed along with each row from the main data source, since there join is undefined, it will display the same value(s) with every row. 

 

Report Data Source join field (Measure-based components)

 

clip0292

 

 

Component Data Source join field (Measure-based components)

 

clip0293

 

Report Data Source join field & Component  Data Source join field (List)

 

clip0294

 

 

Report Data Source

 

The report data source is optional and is used when a report needs to have a Data Field component, data grouping, multiple sources data join, or improve query efficiency.

 

When there is no report data source presented, the report basically works like a dashboard. It has individual components with their own data sources. The components could be in the group header or detail section, it doesn't make a difference.

 

When a report data source is presented, each component with a component data source has the option to join it. A data join is used when a component needs to be part of the report grouping. For example, an opportunity trending chart for a report grouped by account name. Each account needs the trending chart to be limited to its own opportunities. 

 

When a join component is placed inside a group header/footer and the measure inside the component is a (cross object) formula, the join key needs to be the same as the group by field. If it’s not a formula, it needs to be defined as an equivalent or of lower level than the group by field. For example, if the group by field is Account Name, the join key could be opportunity id (lower than account name) or account id (the equivalent of the account name).