DrillableItems

You can enable eventing and drilling in a visualization. Drilling is the process of "zooming in" on a single measure value by filtering out all other data and breaking that value across a new attribute of interest.

To add drilling, use function predicates.

Before Version 6.2, you could implement drilling using a list of drillableItems that contained the URI or identifier of a measure or attribute (for example, { identifier: "label.owner.department" } or { uri: "/gdc/md/workspaceHash/obj/1027" }). While we do not recommend that you use this method anymore, it is still supported. For more information, see DrillableItems in the Version 6.1 documentation.

To turn on eventing and drilling, specify at least one drillableItem.

Drillable items can consist of the following entities:

• Measures

• Attribute displayForms that are defined by their identifier or URI

  displayForm, or attribute label, is a different means of representing an attribute. For example, the Name attribute might have labels for Firstname and Lastname. For more information, see Attributes in Logical Data Models.

• Attribute values defined by their URI

Visualization points that intersect any defined measures, attributes, or attribute values become drillable and will emit events when interacted with.

NOTE: Ad-hoc measures (measures created from attributes or other measures using computeRatio option are defined using their URI or identifier in the execution. If you want to set up drilling for such ad-hoc measures, use the same parameter (URI or identifier) as you used in the execution. Keep in mind that Analytical Designer creates such measures using only the URI. If you want to activate drilling on ad-hoc measures created in Analytical Designer, you can use only their URIs.

Structure

drillableItems: [
    (header: IMappingHeader, context: IMappingHeaderContext) => boolean, // Type: IHeaderPredicate
    ...
]

IHeaderPredicate defines the function that accepts IMappingHeader and context as its parameters and returns a boolean value. This function is executed against every measure and attribute in a visualization. If the function returns true, the measure or attribute is drillable. If the function returns false, the measure or attribute is not drillable.

You can program any logic to determine whether a particular measure or attribute should be drillable. However, this is not required often. For more information, see Create Header Predicates.

Predicate factory helpers

GoodData.UI contains HeaderPredicates that helps you easily build predicate functions that cover most of the common drill eventing use cases. You can import this factory directly from the @gooddata/sdk-ui package.

HeaderPredicates provides the following predicate factory functions:

• uriMatch("<measure-or-attribute-uri>")

  The helper builds a predicate function that matches any measure or attribute in a visualization to the provided URI.

• identifierMatch("<measure-or-attribute-identifier>")

  The helper builds a predicate function that matches any measure or attribute in a visualization to the provided identifier.

• composedFromUri("<measure-or-attribute-uri>")

  The helper builds a predicate function that matches any arithmetic measure in a visualization containing measures to the provided URI in its tree of measures that the arithmetic measure is built from.

• composedFromIdentifier("<measure-or-attribute-identifier>")

  The helper builds a predicate function that matches any arithmetic measure in a visualization containing measures to the provided identifier in its tree of measures that the arithmetic measure is built from.

Set up drilling

To enable event drilling, specify a value for the drillableItems property.

In the drillableItems property, add an array of IHeaderPredicate functions that identifies the measures and attributes that should become highlighted and drillable.

Example: Drilling in a visualization enabled for the measure with either the identifier of label.owner.department or the URI of /gdc/md/la84vcyhrq8jwbu4wpipw66q2sqeb923/obj/9211

// This is an example of event drilling on the visualization from the GoodSales demo workspace.
import { HeaderPredicates } from "@gooddata/sdk-ui";

function onDrillHandler(event) {
    // handle drill
}

<InsightView
  insight="aby3polcaFxy"
  drillableItems={[
    HeaderPredicates.uriMatch("/gdc/md/la84vcyhrq8jwbu4wpipw66q2sqeb923/obj/9211"),
    HeaderPredicates.identifierMatch("label.owner.department")
  ]}
  onDrill={onDrillHandler}
/>

Example: Drilling in a visualization enabled for every arithmetic measure that has a measure with either the identifier set to label.owner.department or the URI set to /gdc/md/la84vcyhrq8jwbu4wpipw66q2sqeb923/obj/9211 in its tree of measures that the arithmetic measure is built from

// This is an example of event drilling on the visualization from the GoodSales demo workspace.
import { HeaderPredicates } from "@gooddata/sdk-ui";

function onDrillHandler(event) {
    // handle drill
}

<InsightView
  insight="aby3polcaFxy"
  drillableItems={[
    HeaderPredicates.composedFromUri("/gdc/md/la84vcyhrq8jwbu4wpipw66q2sqeb923/obj/9211"),
    HeaderPredicates.composedFromIdentifier("label.owner.department")
  ]}
  onDrill={onDrillHandler}
/>

Each event contains an object consisting of dataView and drillContext. dataView contains the underlying data used to render the chart from which the drill event originates. drillContext contains full context of which element the user clicked.

Additional information

For more information, see Setting up Events for Drilling in Embedded Analytical Designer and KPI Dashboards.