Does PBI Report Builder recognize relationships of a PBI Dataset?

[olimilo]

I have Tables A and B in a 1:M relationship, respectively, that I pull from a PBI dataset. I manually plotted the fields of A and B (only 2 fields from B) on a regular data table (one that doesn't need any aggregates of any sort). There should only be 750 unique entries in Table A, and while joined, Table A and B should produce 4.2k entries.

Once published, I see the report generated 72k rows which is obviously not the expected output.

How do I get PBI Report Builder to recognize and apply the relationship that was in the PBI dataset?

[maruthisp · Accepted solution]

Hi olimilo,

As per knowledge, Report Builder doesn't automatically recognize or apply relationships from a Power BI dataset.
You must explicitly define the joins between datasets in Report Builder.
There are some functions in Report Builder to create a proper JOINS between the datatsets.
Below link can help you to understand about LOOKUPS in Report Builder.

SSRS Report Builder Part 7.12 - Lookup, LookupSet and MultiLookup Functions

I may be wrong as well, but try to investiagte once.

If this reply helped solve your problem, please consider clicking "Accept as Solution" so others can benefit too. And if you found it useful, a quick "Kudos" is always appreciated — thanks! 

Best Regards, 

Maruthi 

LinkedIn - http://www.linkedin.com/in/maruthi-siva-prasad/ 

X            -  Maruthi Siva Prasad - (@MaruthiSP) / X 

[v-sgandrathi]

Hi @olimilo,

Thanks for raising this question!

As highlighted by the Community members(Thankyou for your inputs), Power BI Report Builder does not automatically apply model relationships from a Power BI dataset like Power BI Desktop does.

To get accurate row-level output:

• Use a DAX query (e.g., with SUMMARIZE, RELATED, or TREATAS) in the Query Designer to enforce relationships.
• If you're working with separate datasets, use functions like LOOKUP or LOOKUPSET to manually relate them in the report.

Glad I could assist! If this answer helped resolve your issue, please mark it as Accept as Solution and give us Kudos to guide others facing the same concern.

Thank you.

[v-sgandrathi]

Hi @olimilo,

May I ask if you have gotten this issue resolved?

If it is solved, please mark the helpful reply or share your solution and accept it as solution, it will be helpful for other members of the community who have similar problems as yours to solve it faster.

Thank you.

[v-sgandrathi]

Hi @olimilo,

I wanted to check in your situation regarding the issue. Have you resolved it? If you have, please consider marking the reply as Accepted solution and give Kudos that helped you. It would be greatly appreciated by others in the community who may have the same question.

Thank you for using Microsoft Fabric Community Forum.

[v-sgandrathi]

Hi @olimilo,

As we did not get a response, may I know if the above reply could clarify your issue, or could you please help confirm if we may help you with anything else?

And if the provided information meets your requirements, you can Accept the solution and also give Kudos on that reply. It helps other users who are searching for this same information and find the information.

Your understanding and patience will be appreciated.

[Akash_Varuna · Accepted solution]

Hi @olimilo Well, the Report Builder doesn't automatically recognize relationships from a Power BI dataset. Use the Query Designer to write a DAX query (e.g., SUMMARIZE with RELATED) to apply the relationships. Alternatively, define joins manually (e.g., INNER JOIN) in the query editor. 

[maruthisp · Accepted solution]

Hi olimilo,

As per knowledge, Report Builder doesn't automatically recognize or apply relationships from a Power BI dataset.
You must explicitly define the joins between datasets in Report Builder.
There are some functions in Report Builder to create a proper JOINS between the datatsets.
Below link can help you to understand about LOOKUPS in Report Builder.

SSRS Report Builder Part 7.12 - Lookup, LookupSet and MultiLookup Functions

I may be wrong as well, but try to investiagte once.

If this reply helped solve your problem, please consider clicking "Accept as Solution" so others can benefit too. And if you found it useful, a quick "Kudos" is always appreciated — thanks! 

Best Regards, 

Maruthi 

LinkedIn - http://www.linkedin.com/in/maruthi-siva-prasad/ 

X            -  Maruthi Siva Prasad - (@MaruthiSP) / X