Power BI Custom Connector

[KeyurPatel14]

I'm building a Power BI custom connector for an OData API and would appreciate some guidance from the community.

My connector currently allows users to select a table/entity and load data successfully. However, I'd like to enhance the user experience with two additional capabilities:

1. Filter Selection Dropdown

   • Similar to the Advanced Options available in the built-in Web connector, I want to provide users with a dropdown (or similar UI control) to select predefined filter values before the data is loaded.

   • Ideally, the selected value would be passed as an OData filter parameter to the API request.

   • Is there a supported way to create dropdowns or dynamic parameter selection screens in a custom connector?

2. Back Navigation / Re-selection of Table

   • After a user selects a table/entity, I'd like to provide a way for them to go back and choose a different table without having to restart the connection process.

   • Is there any concept of a "Back" button or navigation flow within Power Query custom connectors?

   • If not, what is the recommended approach for handling multi-step selection scenarios?

I've reviewed the custom connector documentation but haven't found clear examples covering these UI/navigation requirements.

If anyone has implemented something similar or can point me to relevant documentation, sample connectors, or best practices, I'd be very grateful.

Thanks in advance!

[v-aatheeque]

Hi  @KeyurPatel14 

The requirements can be handled using the standard Power Query custom connector patterns, although there are some UI limitations.

• Filter dropdown: You can expose predefined filter values through a connector function parameter using Documentation.AllowedValues. This allows Power Query to present the values as a selection list, and the selected value can then be used to construct the OData $filter query. However, custom connectors don't provide a general framework for creating arbitrary UI controls.
  Back/re-selection: Custom connectors don't expose an API to add a custom Back button or control the Navigator's navigation flow. The recommended approach is to return a Navigation Table containing the available entities/tables. Users can then select the required entity from the Navigator rather than restarting the connection.

  Useful Links : https://learn.microsoft.com/en-us/power-query/handling-navigation-tables

  https://learn.microsoft.com/en-us/power-query/handling-resource-path

  https://learn.microsoft.com/en-us/power-query/samples-directory

  Hope this helps !!

  Thank You.