I'm reposting this as I did not get any feasable solutions and I'm pretty sure this topic went stale.
Also, I'm using the May Desktop and Server edition of PBI.
I've got this really strange issue that only rears it's head when viewing my dahsboard from the report server.
A few of my tables have a dynamic X axis, where I can select how I want to view my axis from a slicer drop down.
I've done this by adding an index column to my source data and creating a reference table from it.
Next, I unpivoted the columns in the reference table that I want shown in my slicer drop down.
I create a relationship between the two tables using the Index as the bridge and it's cross filtering in both directions (pic1).
The slicer dropdown field has the ref table "attributes" and the chart axis field contains the "values" from the ref table.
Boom, it works as expected in PBI Desktop. Great!
Here is a pic showing what it looks like and using a page level filter to prove that the data is filtering correctly (pic 2 & 3).
However, when I publish it to the server and it refreshes the relationships go haywire and I get funky data when filtered (pic 4)
ie. When page level filter is for West, Visual should only show the West Divison, not all.
(Just to clarify, the relationships look fine in the server after publishing until I give it a refresh.)
The next thing I do is click "edit in PBI Desktop" and once it's on my desktop, what do you know, all the realtionships are fixed again and the report functions as intended without me doing anything.
So why are the relationships getting skewed in the report server, but get fixed automaticaly once I pull the report into the Desktop app?
I can asume something with the indexes is going off the rails during the refresh, but then why the automatic fix once pulling the report into the desktop app.
Can anyone please provide me with some insight on this issue i'm having?
Relationship set up:
Works in Desktop App
Does not work when server refreshes
I'm glad to find a post exactly the same issue I'm encountering these past few months.
It happens 1 to 3 times out of 4 auto-refresh. The current fix is to refresh manually the dataset AND the reports. Sometimes I have to refresh datasets and reports more than 2 times in order to get the correct match in my dynamic Y axis.
On the other hand, I created another report: merger ref table and fact table in order to remove a relationship. It hasn't had the same issue no more. However, there is a column that full of repetitive values, which is against to star schema.
Is there any solution for this post yet?
@tmendoza - Very difficult to follow. I recommend creating a sample dataset that emulates this behavior and posting it so that others can replicate the behavior and troubleshoot. Otherwise, You could check the Issues forum here:
And if it is not there, then you could post it.
If you have Pro account you could try to open a support ticket. If you have a Pro account it is free. Go to https://support.powerbi.com. Scroll down and click "CREATE SUPPORT TICKET".
Sorry it's a little hard to follow, but what I'm really trying to ask is:
Do you know why relationships would break during a server refresh and get fixed automatically when pulling into the desktop app?
Check out the November 2023 Power BI update to learn about new features.
Read the latest Fabric Community announcements, including updates on Power BI, Synapse, Data Factory and Data Activator.
130+ sessions, 130+ speakers, Product managers, MVPs, and experts. All about Power BI and Fabric. Attend online or watch the recordings.