Forum Discussion
Differences between Datasets and Reports
Hi Ibendlin,
Thanks very much for your reply, and apologies for my delay; I didn't get a notification.
What you say above makes sense, but I'm still unclear on how fields can work in the PBIX model but not in the report file providing I've done as you say (publish both files, then schedule after). Everything I'm doing at the moment is in Desktop, let's leave the workspace for now.
A little more context to my issue, I have a standard TimePeriod table which is joined to a financial targets table via the Calendar Start Date field. The cardinality is many to many. To test the model, I built the chart in my PBIX file and everything was fine. I then published the model and opened a new project and connected to it, when I then created the same chart, the data wasn't showing (table and fields were available but they yielded nothing on the visual). Coming from a Tableau background, my mind went to the relationship but given it acted as expected in the PBIX, but I'm doubtful as it was working as intended in the model file when I created a chart.
Since then I deleted the targets table which was stored outside PowerBI and replicated the table inside the application. Still though, when using the fields within the model file, things show up, but after I've published the model and create a new project using the model, the charts don't work. The first image is a picture of the chart using the PBIX, the second is the exact same conditions but in the new report file.
At the moment, these are both via the desktop application.
The cardinality is many to manyYou want a 1:* relationship from the calendar table to the fact table, with single direction.
The cardinality is many to manyYou want a 1:* relationship from the calendar table to the fact table, with single direction.
It has to be many to many I believe, as there's a region column in the Targets table, so each region has a target per month. Setting the cardinality to anything other than many-to-many produces an error.
It also works as intended in the model file, but not in the report. Surely if the cardinality was incorrect the model simply wouldn't serve up what I need in either file?
Here's a dummy of what the two tables look like, I've tested these outside the main model (which is vast), and pretty sure the relationship is configured correctly... though perhaps I need to bring in another fact table.
