Creating and sharing multiple reports using the same Power BI Service Dataset

[AEIOUandY]

I'm currently working on a series of reports that I intended to use a singular dataset hosted on the Power BI Service to populate. That dataset uses a gateway connection to an on-premise SQL server DB. I created a report and dataset and published to the service. I then created new reports (on Desktop) using that Power BI Service data but noticed that rather than simply loading the entire data model as before, there is an additional prompt where I can select specific tables or all tables from that model.

Once published to the Service, rather than connecting to my original Data file, a 'child' data file is created, which uses a Personal Cloud Connection to draw from the first Data file. Additionally, I cannot generate public embed codes for any of the the reports I've built that now reference their own 'child' datasets rather than the original.

Can you tell me whether it's possible to directly connect to the original published dataset on the Service as I was previously able to do, if that's indeed still possible, or how I can go about getting an embed code to generate (there appears to be no way besides using a Personal Cloud Connection to connect to my original dataset).

I'm lost. Please help.

[AEIOUandY · Accepted solution]

No solution really helped, I had the experience of having some reports from which I removed the data connections for which I WAS able to successfully create a live connection to my master report, and some reports from which I removed the data connections for which I WASN'T able to successfully create a live connection to my master report with all of the previous data removed. 

I don't know what differentiated the successes from the failures, my solution was to rebuild the failures by copying the visualizations into a new blank report and THEN create a live connection to the dataset on the PBI Service, and rebuild the bookmarks, tabs, etc. afterward. I had been hoping to avoid the work of setting up all of my navigation again, but lesson learned, I guess. Even though the file SEEMS to remove all data connections, for whatever reason it wouldn't let me establish a live connection afterward, even though I had full access/permissions to do so (and was in fact able to do so with other already populated files (where the data model was deleted) and with brand new files (as would be expected, as no data model had previously existed to conflict with the new one). 

I might need to mark this as solved by me but not in the way I was hoping.

[AEIOUandY]

I appreciate the reply, @GilbertQ. I had already been through that webpage's list of don'ts and it unfortunately didn't help.

Previously when selecting a Power BI Service dataset, we selected the set and that was it - there was no popup to choose the whole set or only selected tables from it. I don't know what implications that has, but noticed the child data model springing up now that this new step has been added. I feel this is not a coincidence. The reports I'm designing are in no way different from what I had previously created and published and embedded to websites using this method. I'm not using RLS on the original dataset. I'm not using ANY additional measures (no report-level DAX measures) in my new reports - the data model is unchanged. 

Where SHOULD I see the "Connected live ..." banner? Under the ribbon? I definitely am NOT seeing that and it hadn't dawned on me that something is up with my data connection. When I view the Data Sources, it's listed as a "Direct Query to AS - Power BI Dataset;DatasetName". AS is our org Fabric admin's initials, so I assume that refers to them, and our gateway is setup as an on-prem gateway with me added as a "connection creator with resharing". 

[GilbertQ]

Hi @AEIOUandY 

As far as I know if you had to select the Power BI dataset when connecting it should work without having another child data file.

When connecting to the dataset in the Power BI Service make sure to select "Power BI Dataset"

Then make sure that when you have your report open it says "Connected live to the Power BI Dataset"

If it does not say the above it will create a child data file.

For the publish to web it will not work with the child dataset, you have to connect in the above way. Here is a link to the limitations below.

Publish to web from Power BI - Power BI | Microsoft Learn