Transitioning to PBI from Business Objects

[rnola16]

We are in process of transitioning from Business Objects to PBI, where it includes 300 odd templates to be reproduced in PBI. Our underlying db is Teradata and the tables are huge with billions or records. Currently users run the template in Business Objects where it includes parameters on date/id etc and schedule them. 

If we are to replicate this in PBI with user input parameters on the tables, is it possible in Power BI.

Eg: 

Select a.recordID, a.date

From

Table a

where

a.recordid= Parameter_recordid and 

a.date = Parameter_startdate

So in here the sample query has paramenters in recordid and date which works good in Business Objects, what is an ideal approach in PBI. Use a direct query or import query ? Can these template be created with user defined parametes dynamically and scheduled ?

Thanks.

[rohit1991]

Hi,

Moving from Business Objects to Power BI is a big step, but you’ll find the flexibility in Power BI is really powerful, especially with huge Teradata datasets. Here’s how you can handle parameters, templates, and scheduling:

1. Parameters and Filtering: In Power BI, you don’t typically prompt for parameters like in BO. Instead, you set up slicers or filter panes on your report, so users pick things like date, recordID, etc. right in the dashboard. For advanced scenarios, you can use Dynamic M Query Parameters, this lets your slicers pass values directly to your SQL (DirectQuery) so only filtered data gets queried.
   
   

2. DirectQuery vs Import: With Teradata and billions of rows, DirectQuery is the way to go. This means the data stays in your database and queries are run on-demand, so you’re not loading massive tables into Power BI. Import is only practical if you’re pre-aggregating or pulling summary data.
   
   

3. Report Templates and Scheduling: Templates in Power BI are reusable report layouts with slicers for user selection. If you want BO-style parameter input forms and pixel-perfect scheduled exports, check out Paginated Reports (Power BI Report Builder). These are made for operational/report-bursting use cases.
   
   

4. Scheduling: Use Power BI Service to schedule dataset refreshes and set up report subscriptions, especially with Paginated Reports.
   
   

Use DirectQuery for your main reports, and design them with slicers for recordID, date, and any other key fields. If your users really need the classic “enter parameter and run” experience, Paginated Reports are a great fit as they support parameters and scheduled distribution.

[lbendlin · Accepted solution]

Direct Query with dynamic M parameters

Dynamic M query parameters in Power BI Desktop - Power BI | Microsoft Learn