Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Join us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.

Reply
ahmedshalabyy12
Helper II
Helper II

Paginated Reports

Hello,

 

I have table x   and made a relation with date table.

 

in power bi desktop the relation is working fine and i can filter the x table with the date column from date table

 

but in paginated report the paramteres not working 

1 ACCEPTED SOLUTION
burakkaragoz
Community Champion
Community Champion

Hi @ahmedshalabyy12 ,

 

This is a common issue when moving from Power BI Desktop to Paginated Reports. Even though the relationship works fine in the model, paginated reports don’t automatically inherit those relationships for parameter filtering.

Here’s what you can try:

  1. Make sure your dataset includes the necessary joins: In paginated reports, you often need to explicitly define the relationship in your query (like using a JOIN between table x and the date table).

  2. Check your parameter setup: If you're using a date parameter, ensure that:

    • The parameter is linked to the correct dataset.
    • The dataset query uses the parameter in the WHERE clause (e.g., WHERE DateTable.Date = @YourDateParam).
  3. Use shared datasets carefully: If you're using a shared dataset from Power BI, it might not expose the relationships the same way as in Desktop. You might need to flatten the data or create a custom SQL query in the report builder.

Let me know how your parameters are set up and I can help you tweak the query if needed.

If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
translation and formatting supported by AI

View solution in original post

3 REPLIES 3
burakkaragoz
Community Champion
Community Champion

Hi @ahmedshalabyy12 ,

 

This is a common issue when moving from Power BI Desktop to Paginated Reports. Even though the relationship works fine in the model, paginated reports don’t automatically inherit those relationships for parameter filtering.

Here’s what you can try:

  1. Make sure your dataset includes the necessary joins: In paginated reports, you often need to explicitly define the relationship in your query (like using a JOIN between table x and the date table).

  2. Check your parameter setup: If you're using a date parameter, ensure that:

    • The parameter is linked to the correct dataset.
    • The dataset query uses the parameter in the WHERE clause (e.g., WHERE DateTable.Date = @YourDateParam).
  3. Use shared datasets carefully: If you're using a shared dataset from Power BI, it might not expose the relationships the same way as in Desktop. You might need to flatten the data or create a custom SQL query in the report builder.

Let me know how your parameters are set up and I can help you tweak the query if needed.

If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
translation and formatting supported by AI

thank you any way for your support and help 

That's my query iam trying with chat gpt to solve it 
but if you can help me with it 

EVALUATE
SUMMARIZECOLUMNS (
'Csat'[agent_email],
'Csat'[agent_name],
'Csat'[artificial_ou],
'Csat'[country_name],
'Csat'[artificial_ou_region],
'Csat'[badge],
'Csat'[city_name],
'Csat'[close_timestamp],
'Csat'[count_agent_messages],
'Csat'[create_timestamp],
'Csat'[csat_issue_name],
'Csat'[csat_issue_type],
'Csat'[csat_rating],
'Csat'[DSAT_category],
'Csat'[DSAT_L2_category],
'Csat'[fulfillment_type],
'Csat'[global_product_name],
'Csat'[has_appeasement],
'Csat'[max_load_timestamp],
'Csat'[mega_region],
'Csat'[merchant_location_type],
'Csat'[merchant_type],
'Csat'[modality],
'Csat'[ticket_url],
'Csat'[net_handle_time_minutes],
'Csat'[network_custom_language],
'Csat'[network_custom_region],
'Csat'[network_custom_tier],
'Csat'[network_requester_type],
'Csat'[nosat_reason],
'Csat'[operational_unit],
'Csat'[ou_region],
'Csat'[queue_name],
'Csat'[report_day],
'Csat'[requester_uuid],
'Csat'[site_code],
'Csat'[text],
'Dim_date'[date],

RSCustomDaxFilter(
@date,
EqualToCondition,
[Dim_date].[date],
DateTime
),

RSCustomDaxFilter(
@sitecode,
EqualToCondition,
[Csat].[site_code],
String
),

RSCustomDaxFilter(
@operationalunit,
EqualToCondition,
[Csat].[operational_unit],
String
),

RSCustomDaxFilter(
@agentemail,
EqualToCondition,
[Csat].[agent_email],
String
)
)

Helpful resources

Announcements
July PBI25 Carousel

Power BI Monthly Update - July 2025

Check out the July 2025 Power BI update to learn about new features.

Join our Fabric User Panel

Join our Fabric User Panel

This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.

June 2025 community update carousel

Fabric Community Update - June 2025

Find out what's new and trending in the Fabric community.