Forum Discussion
Help needed for Power Bi Paginated report builder
Hi, ashmitp869
Thank you for your inquiry. Regarding the issue you mentioned, when you create a paginated report in Power BI Paginated Report builder using the semantic model of already established relationships, those relationships are not automatically inherited.
To verify this, I ran the following test: I created two data tables and published them to the Power BI Service. Subsequently, I used this semantic model in Power BI Paginated Report builder to create a paginated report.
Use this semantic model in Power BI Paginated Report builder:
It's clear that there are a few more rows in the paginated report builder that don't actually exist. For example, for 1 Order Num, the corresponding Sales Amount is only 100, 200, 300 if the relationship is already established.
In order to use relationships between tables in Power BI Report Builder, we recommend that you consider the following two approaches:
1. Use Power BI to build a normal report. This ensures that all the relationships and filters you create in Power BI are applied correctly, and that the interactivity and consistency of your reports are maintained.
2. Use a SQL Server database. If you want to use relationships between tables in Report Builder, we recommend that you store the data tables in a SQL Server database. When you build a dataset for a SQL Server data source in Report Builder, you can use these relationships to build paginated reports.
Salestable:
OrdersTable:
With SQL Server, we can see that relationships are working properly.
Best Regards
Jianpeng Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi Jianpeng,
Thanks for the reply. Will you please help me with the dax query.
Here is my query in Paginated Report.
EVALUATE SUMMARIZECOLUMNS('PayItem'[ProjectId], 'PayItem'[PayItemId], 'PayItem'[PayItemNumber], 'PayItem'[Description], 'PayItem'[UnitOfMeasureName], 'PayItem'[ForecastTakeOffQuantity], 'PayItem'[ForecastUnitRevenue], 'PayItem'[ForecastFinalRevenue], 'Projects'[Project_id], 'Projects'[Project ID], RSCustomDaxFilter(@ProjectsProjectID,EqualToCondition,[Projects].[Project ID],String))
I need to Join with 'PayItem'[ProjectId] and 'Projects'[Project_id] . As I did it in my Semantic Model.
I thought it will done by its won but not.
I have tried this query:
EVALUATE
SUMMARIZECOLUMNS(
'PayItem'[ProjectId],
'PayItem'[PayItemId],
'PayItem'[PayItemNumber],
'PayItem'[Description],
'PayItem'[UnitOfMeasureName],
'PayItem'[ForecastTakeOffQuantity],
'PayItem'[ForecastUnitRevenue],
'PayItem'[ForecastFinalRevenue],
'Projects'[Project_id],
'Projects'[Project ID],
RSCustomDaxFilter(
@ProjectsProjectID,
EqualToCondition,
[Projects].[Project ID],
String
),
'Projects'[Project_id] = 'PayItem'[ProjectId]
)as well but giving me this error.
Any help please
I am expecting they should be same.
Hi, ashmitp869
There is a problem with the following part of your DAX expression:
Such writing is not supported in DAX. You can check to see how filter is written in my query DAX expression:
You can edit your query directly in the Query Designer. You can match the two tables as shown above.
Best Regards
Jianpeng Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
