Relationships Break When Server Refreshes
Hello All, 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: Finished Product Works in Desktop App Does not work when server refreshes
Broken relationship after RS refresh
Hi I have an issue where resfreshing my data on Report Server breaks one of my datasets relationships to the date table. The relationship is ok when refreshing the data in PowerBI desktop RS. The relationship is ok when saving or overwriting the report to RS. The relationship breaks after any scheduled refresh on RS. (Refresh is reported successfull) e.g. goes from this: to this: I've gone into options and turned off these options Running RS Jan21
Relationship to Unpivoted Reference Table incorrect only in Report Server (pics included)
Hello all, 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?
