I'm developing a new report for my work. For corporate reasons, I obviously can't go into much detail, but one key point of it is the age of the records. I have a boolean column that returns TRUE if the record is 30 days or over and FALSE if it is under 30 days. I then created three pages, two of which are filtered by that column - a page with records with 30 days or older, another with records younger than 30 days and a third one with all the records, ie, no filter.
However, when creating the column, I initially based it on another datetime column. I caught the mistake and, for code cleanliness reasons, recreated it with the same name in a different step of the PQ query.
Yesterday, I sent a link (let's call it Link A) to a couple of stakeholders so they could give me feedback and one of them replied that the age of the records on the "Older than 30 days" page seemed off. I quickly identified the problem - I had corrected the page-wide filter on the two other pages, but not that one. So, I corrected it to use the new column, re-published and told her to take a second look. She told me it hadn't changed which seemed strange because I clicked the link in PowerBI desktop right after publishing and it was working as expected. So, I clicked "Share" again and sent her the link (Link B) and she could now see the corrected version, which seemed to kill the issue.
Except I decided to test Link A and, yes, I, too, could see the broken version. So, I now have a dashboard which, depending on which link you click, shows two different versions, which are exactly the same in everything except for the mentioned filter.
Notes:
- No, I didn't post to different workspaces (I only have one, anyway);
- The only difference in the URLs seems to be the "bookmarkGuid" parameter. If I delete that parameter and hit Enter, I get Link A's version (the broken one). The rest of the URL is exactly the same. Since I didn't create any bookmarks on the dashboard, I'm guessing this "bookmark" is a different thing from the ones we define when creating the report (as this report doesn't have them);
- Sources for the report are an SQL query against our Data Mart and an Excel workbook;
- While writing this message, I got a notification that our Data Mart updated, so I refreshed the data (it's still not connected to the gateway) and re-published it - the issue persists;
- Workaround would probably be to delete the report (which I *think* would invalidate both links) and re-upload it, but I'd like to know if anyone has seen this behavior and has alternative suggestions before going this route.
