Navigating to Related Items in Connector using Power BI

This article covers a detailed technical subject for using Power BI to access Connector Read APIs. For more background on the basics of using Power BI with Connector, go to Accessing Connector Read APIs from Power BI.

While each dataset provided by the Connector Read APIs can stand alone, many also have relationships to other datasets.

Example: The Suppliers dataset has a relationship to the Parts dataset, allowing users to identify which Parts are associated with each Supplier.

The data transformation tools in Power BI make it easy to find and navigate these relationships, but the OData queries created for the navigation have a known bug that results in an error, and users creating a report with relationship navigation will need to make a manual correction to the underlying query.

The example below has configured a report based on the Suppliers dataset, and the user has selected to include information from the associated Parts for each supplier.

Using the Transform Data tools to select columns and related datasets

However, when the user attempts to expand the Parts column to include columns from that dataset, they get an error:

Error when attempting to navigate an OData relationship

To avoid this error, the user will need to manually change the underlying OData query, removing an “Implementation” flag that has an obsolete value that interferes with the navigation. The user will need to make the following change in the Source tab, replacing [Implementation=”2.0”] with null.

OData.Feed("https://eval.grandavenue.com/Acme/odata/v2", null, [Implementation="2.0"])

OData.Feed("https://eval.grandavenue.com/Acme/odata/v2", null, null)

Once this change is made, the navigation should work correctly.

Related Pages

How do I Use the GAS API?

Accessing Connector Read APIs from Excel

Accessing Connector Read APIs from Power BI