Forum Discussion
Power BI custom connector
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:
- 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?
- 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!
Hi VedantChauhan,
Thanks for reaching out to the Microsoft Fabric Community forum.
For the filter selection requirement, Power Query custom connectors support function parameters with predefined values. Using Documentation.AllowedValues changes the parameter input from a text box to a drop-down list. The selected value can then be handled by the connector logic when constructing the API request.
For table/entity selection, the documented approach is a Navigation Table. Power Query displays the Navigator after the required parameters and authentication. Navigation Tables can also be nested/multi-level, allowing hierarchical selection of entities.
For the navigation flow, the documented approach is to use Navigation Tables, including nested Navigation Tables for multi-level selection.
A suitable flow would therefore be:
Parameters → Authentication → Navigation Table → Entity/Table selection → Data retrieval
For more information, please refer to the below official Microsoft documentation:
Add Function Documentation - Power Query | Microsoft Learn
Handling navigation for Power Query connectors - Power Query | Microsoft Learn
Handling navigation for Power Query connectors - Power Query | Microsoft Learn
I hope this helps. Please feel free to reach out if you have any further questions.
Thank you.
4 Replies
Hi VedantChauhan,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
Thank you.Yes v-abhinavmu,
Thank you for the quick answer
It worked with certain changes needed on my side!!Hi VedantChauhan,
Thank you for the update and for confirming that the solution worked with the required changes on your side. Glad to hear that you were able to get it working successfully.
I appreciate you taking the time to confirm the outcome. This should also be helpful for others who may come across a similar requirement.
Thank you!
Hi VedantChauhan,
Thanks for reaching out to the Microsoft Fabric Community forum.
For the filter selection requirement, Power Query custom connectors support function parameters with predefined values. Using Documentation.AllowedValues changes the parameter input from a text box to a drop-down list. The selected value can then be handled by the connector logic when constructing the API request.
For table/entity selection, the documented approach is a Navigation Table. Power Query displays the Navigator after the required parameters and authentication. Navigation Tables can also be nested/multi-level, allowing hierarchical selection of entities.
For the navigation flow, the documented approach is to use Navigation Tables, including nested Navigation Tables for multi-level selection.
A suitable flow would therefore be:
Parameters → Authentication → Navigation Table → Entity/Table selection → Data retrieval
For more information, please refer to the below official Microsoft documentation:
Add Function Documentation - Power Query | Microsoft Learn
Handling navigation for Power Query connectors - Power Query | Microsoft Learn
Handling navigation for Power Query connectors - Power Query | Microsoft Learn
I hope this helps. Please feel free to reach out if you have any further questions.
Thank you.
