Board planning data into your Azure data warehouse and Power BI
Planning & analytics from Board
Yres offers Board as its own entry in the source list. You enter three details: the server, the application and the identity provider of your Board environment. Sign-in uses OAuth2 client credentials, through an OAuth client you create in Board. Under the hood Yres uses its generic REST connector: the JSON from Board is parsed into tables inside your Azure SQL database and then follows the normal load route with history, so you can place planning figures next to your actuals in Power BI.
At a glance
- Connection
- Dedicated source entry for Board (Board EPM), which uses the generic Yres REST connector under the hood
- What you enter
- Server, application and identity provider of your Board environment
- Authentication
- OAuth2 client credentials, with an OAuth client you set up in Board
- Where it runs
- As Azure Data Factory pipelines in your own Azure tenant. The cloud runtime is usual; a self-hosted integration runtime is possible if your environment is shielded
- Client secret
- Kept in the Key Vault of your own Azure environment; the Yres web application stores no secrets
What you arrange yourself
- 1Set up an OAuth client in Board and note the client ID and client secret.
- 2Note the server, the application name and the identity provider of your Board environment.
- 3Add the Board source in Yres and enter these details.
- 4Add the tables you want to load and schedule the refresh.
When you need this — and when you don't
A standalone connector is enough if…
If planning, forecasting and reporting all stay inside Board, you do not need a separate data warehouse.
Yres adds value if…
Yres earns its place once budget and forecast figures from Board must sit next to actuals from your ERP or HR system, in one Power BI model, or when you want to keep what a plan looked like on an earlier date.
Frequently asked questions: Board
How does Yres authenticate with Board?
With OAuth2 client credentials: a system-to-system sign-in that needs no user to log in. You create an OAuth client in Board for this. Yres additionally asks for the server, the application and the identity provider of your environment.
Is the Board connection a separate connector?
Board has its own entry in the source list with its own fields, but technically the connection rides on the generic Yres REST connector. JSON handling therefore works the same as for any other REST source: tables are created and extended automatically.
Which Board data can I load?
That depends on what your Board environment exposes through its API. The Yres documentation defines the connection details and the sign-in, not a fixed list of Board objects. Get in touch if you want to check beforehand whether your scenario fits.
Do I need a self-hosted integration runtime for Board?
Usually not. For REST sources such as Board the standard cloud runtime of Azure Data Factory is the usual choice. A self-hosted integration runtime is an option if your Board environment cannot be reached directly from Azure.
Full technical description in the knowledge base →·Last reviewed:
Data warehouse automation that runs in your own Azure
Built for organisations on Azure and Power BI. Yres connects your sources, keeps the history and promotes changes in a controlled way, without manual work.