FlowsBook a callSign inCreate free accountSign up
Business and places data

How to keep business data in Power BI up to date without exports

A live CSV or JSON feed lets a Power BI report read a list of businesses by itself. What the feed carries, how often to refresh it, and how to stop it.

Part of the guide Location intelligence automation

By the xMap team · · 6 min read

The simplest way to keep business data in Power BI current is to stop exporting files and give the report a web address to read instead. In xMap Flows, an AI employee finds the businesses on a timetable, and a Live feed on the Results page turns what it found into a CSV address (and a JSON one). Power BI reads that address each time it refreshes, so the report follows the list with nobody downloading or uploading anything.

This guide is for analysts and operations people who already have a dashboard and want a list of outlets, competitors, branches or leads inside it. It covers what the feed holds, how to connect it, how often a refresh is worth doing, a made-up example, and how to switch a feed off.

Why a feed beats a weekly export

An exported file is a photograph: it is right on the day it was taken. Each week someone has to export again, rename the file, replace the old one and hope the columns did not move. A feed is one address that always answers with the latest results, in the same columns, so the only moving part left is the refresh timetable of the report.

The work splits in two. A flow does the finding: for example a Schedule, an Area of interest and Nearby places, which reads xMap's places database for the types of place you pick. Whatever reaches the end of a real run is kept on the Results page. The feed then publishes those results to your dashboard tool. This is ordinary workflow automation, with the report as the last step.

What the feed carries

A feed can cover one flow, one of your saved views (a set of filters you named on Results), or all the results you can see. It holds up to 5,000 results, newest first. There are two choices of fields:

  • Plain facts, the default: the name, kind of place, city and address, rating, website, phone, score, position and the other plain fields the flow found. These are the same facts a public link shows.
  • The team's working fields, which only an organization admin can add: when each result was first and last found, how many times it was found, and which flow found it.

A feed never holds your notes. Fields differ from flow to flow, because a flow that adds population or footfall to each place has more columns than one that only lists places. For a tidy table, feed one flow or one saved view per query instead of everything at once.

Connecting the report

  1. On Results, press Live feed, choose the flow or saved view and the fields, and copy the CSV address. It is shown once, so paste it somewhere safe straight away.
  2. In Power BI Desktop choose Home, Get data, Web, paste the address and pick Anonymous. The feed arrives as a table with one row per result.
  3. Check the column types: rating and score as numbers, the position columns as decimal numbers, dates as dates.
  4. Publish the report and set its scheduled refresh in the Power BI service.

The same address works in a spreadsheet's From Web import and in any tool that reads CSV from a web address; the JSON address is there for scripts and data loaders. The help article Results in Power BI, Looker Studio or Excel has the steps for each.

How often to refresh

Match the refresh to the flow, not the other way round. The feed only changes when the AI employee runs, so a flow that works every Monday morning needs one refresh a week, a little after it finishes. Refreshing every hour reads the same rows again and again. Each feed answers up to 120 reads an hour, which is far more than a sensible timetable needs, and a report that asks too often is simply told to wait.

It also helps to know how fresh the source is. Nearby places reads a database that is refreshed every month, which suits market counts and outlet lists. For places that appeared this week, a flow built on Map business scan searches online maps live on each run.

A made-up example: outlets by suburb

The figures here are invented to show the shape of the work. Say a drinks distributor in Melbourne wants its sales dashboard to show every cafe and bar in six inner suburbs, with a count of the ones that are new.

  • The flow runs every Monday at 06:00: Schedule, an Area of interest with the six suburbs, Nearby places for cafes and bars, then Remove duplicates.
  • An admin makes a feed of that flow with the working fields, so each row carries the day it was first found.
  • The report refreshes on Mondays at 08:00. One page counts outlets by suburb, say 410 in all, with 12 first found in the last 30 days. Another maps them by position and colours them by rating.
  • A sales manager filters the table to independents rated 4 or more and exports nothing: the list is already in the report every Monday.

Nothing in that chain needs a person after the first set-up, which is the whole point.

Mistakes to avoid

  • Treating the address as harmless. Anyone who has it can read the feed. Keep it in the data source settings, not in a slide or a chat message.
  • Expecting statuses or notes. The feed carries facts about each business, not what your team wrote about it.
  • Reading a row count as a market size when the list is larger than the feed's limit.
  • Mixing every flow into one table. Columns that exist for some rows and not others make measures unreliable.
  • Forgetting who made it. A feed shows what its maker can see, and it stops when that person leaves the organization.

Stopping a feed

Feeds are listed on Results, Shared links, with what each one covers and how often it was read. Stop ends it at once: the address answers nothing from that moment, and the report's next refresh fails, which is your reminder to remove the source. A feed also stops by itself when its flow is archived or its saved view is deleted. To change who can read the data, stop the old feed and make a new one; the new address is different.

Questions

Can Power BI read a list of businesses without a file export?

Yes. A Live feed in xMap Flows gives a CSV address that Power BI reads through Get data, Web. Each refresh brings the latest results the flow found.

How many rows does a feed hold?

Up to 5,000 results, newest first. For more, split the list into saved views or write each run into your own database and connect the report to that.

Does the feed include my team's notes?

No. It carries the plain facts of each result, and an admin can add when it was first and last found, how often, and the flow's name. Notes are never included.

How often should the report refresh?

As often as the flow runs. The feed only changes after a run, so a weekly flow needs a weekly refresh shortly after it finishes.

How do I stop a feed?

Open Results, Shared links and press Stop next to it. The address stops working at once. Archiving the flow or deleting the saved view also ends it.

Templates that do this

Read next

More on business and places data · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.