Skip to main content

Seamless Integration: Connecting Yeeflow with Microsoft Power BI

Install the Yeeflow connector, authorize access, invoke data-list queries in Power Query, and check imported data before building or refreshing a Power BI report.

Use the Yeeflow connector to bring authorized data lists into Power BI Desktop, prepare the data in Power Query, and build a report. This guide covers the desktop import process. Publishing a report and refreshing its data in the Power BI service require additional configuration.

Before starting, check that you have Power BI Desktop on Windows, permission to use custom connectors, and access to the Yeeflow lists you need.

Step 1: Install Power BI Desktop

Install Power BI Desktop using your organization’s approved Windows installation method. Microsoft’s Power BI Desktop installation guide

Step 2: Download the Yeeflow Connector

Download YeeflowConnector.mez from Yeeflow. Use the Yeeflow connector for your Yeeflow account; the China edition uses a separate YeeOffice connector.

Step 3: Install the Yeeflow Connector

Close Power BI Desktop. Place YeeflowConnector.mez in your Windows user’s Documents folder, under:

[Documents]\Microsoft Power BI Desktop\Custom Connectors

Create the folders if necessary. If Documents is redirected to OneDrive or another location, use the actual Documents folder rather than assuming its path. Restart Power BI Desktop after installing the connector. Microsoft custom connector installation

Step 4: Adjust Security Settings for Data Extensions

If the connector is blocked, follow your organization’s trusted-connector process. Power BI Desktop’s default security setting allows certified or trusted extensions.

For an uncertified connector that your organization permits, open File → Options and settings → Options → Security. Under Data Extensions, the (Not Recommended) Allow any extension to load without validation or warning option permits unsigned extensions. Enable it only if you trust the connectors being loaded and your organization allows this setting; then restart Power BI Desktop. A trusted signed connector is the alternative described in Microsoft’s connector security guidance.

Step 5: Open Yeeflow Power BI Connector

  1. In Power BI Desktop, select Get data.

  2. Search for Yeeflow, or look under Online Services.

  3. Select Yeeflow (Beta) and then Connect. If it is missing, check the connector folder, extension policy, and whether you restarted Desktop.

Step 6: Connect to Yeeflow Account

Choose the authentication method permitted by your organization. A successful sign-in establishes credentials; confirm the correct organization and available data separately.

Option 1: API Key

Choose Feed Key in the authentication dialog. Obtain an API key approved for this reporting use from your Yeeflow administrator, enter it in the credential field, and select Connect. Keep the key in your organization’s credential management process rather than in a report description or shared screenshot.

Option 2: User Account

Choose Organizational account → Sign in. Confirm that the Yeeflow login page uses login.yeeflow.com, complete sign-in, and choose the intended organization if prompted. Return to the connector dialog and select Connect.

Use an account authorized for the intended lists. If a list is missing after signing in, check the account, organization, and list access before changing the query.

Step 7: Selecting Data Lists and System Built-In Data

In Navigator, expand an application to see its data lists. Select the lists you need, then select Transform Data to open Power Query Editor. At this stage, some selected items are functions that still need to be invoked before they become data tables.

The connector also exposes built-in users, departments, user groups, locations, and positions. The original connector guidance requires system administrator permissions for built-in data. Confirm that access before including these sources in a report.

Step 8: Invoking Data from the Power Query Editor in Microsoft Power BI

Select a function in the Queries pane and fill in its displayed parameters:

  • ListID identifies a business data list. Use that list’s Key value in the navigation formula bar, as shown in the original connector interface. Keep it as text and do not substitute the application ID or a record ID.

  • RangeStart and RangeEnd supply the date/time range. For the business-list function LoadListDataByModified, the range relates to modification time, rather than the record’s creation date.

  • Built-in functions display RangeStart and RangeEnd without ListID. Do not assume every built-in function applies a date filter: check the returned records for the source you selected.

Power Query’s RangeStart and RangeEnd inputs above the Invoke and Clear buttons.

Start with a small date window containing known test records. Select Invoke, inspect the resulting table, and give it a recognizable name. Repeat for each required function.

Check a record inside the window, records near both boundaries, the returned columns, date/time values, and a period with no expected matches. An empty table can be a valid result; an error needs investigation. If expected rows are missing, check list access, ListID, and the modification-time range before building visuals.

After applying the required transformations and checking column types, select Close & Apply. This loads the prepared tables into the report model. Supplying these date parameters alone does not configure Power BI’s incremental-refresh policy.

Step 9: Create Reports with Power BI

Expand a loaded table in the data/fields pane and use its columns to build a table, chart, or other visual. Compare a few known records and a total against the Yeeflow source before sharing. To revise transformations, use Transform data to reopen Power Query Editor; older versions call this Edit Queries.

For this import workflow, report visuals use the data already loaded into the model. Run Refresh in Desktop and recheck a known source change. Merely reopening a visual does not fetch new Yeeflow records into an imported model. How Power BI data refresh works

For online use, follow Publishing Power BI reports. Service refresh is separate from desktop success: configure the custom connector on an appropriate gateway, its accessible connector folder, service-side data source credentials, and the model’s connection. Custom connectors need a TestConnection implementation for gateway use. Microsoft custom connector gateway requirements


Run an on-demand service refresh and check refresh history and one known record before enabling a schedule. See Auto refresh with the Yeeflow connector. Desktop sign-in, report publication, and a successful service refresh are separate checks.

Did this answer your question?