Supplies are limited. Contact info@espc.tech right away to save your spot before the conference sells out.
Get your discountScore big with last-minute savings on the final tickets to FabCon Vienna. Secure your discount
Hello All,
I know some similar questions have been answered but I havent been able to find the answer to mine yet so any help is greatly appriciated.
Imbuilding reports using the desktop app, im using 7 sources. 5 Are a folder on a network drive and 2 are semantic models published by the org already. I have permissions to build and access all of the data however when i connect to a semantic model and a folder as a data source I get missing connection detials when published. (shown below)
If i publish with only the semantic models or only the folder then the repective reports work.
I know the IT have mapped the folders to the gateway (I dont have admin access to the gateway) but i can see all of the folders and i know they added a root folder in case i want to add more.
I need to use DirectQuery and a local model. When building everything is there but publised half of the report is missing.
1. Is there anything I can do on the build side to fix it?
2. what causese the split to happen, the connection to analysis server to dissapear?
3. Are there any suitable work arounds? Its a good chunk of data i need.
For reference the live semantic model data is order and shipment details at a sku level. The folders are a combo of invoices and top level shipping data not in the system. I need to combine them so when a user selects a shipment ID or vessel ID the live model brings back all the warehouse data in regards to them.
Thank you in advance for any help.
G
Hi @GaryAtGW ,
Following up to see if your query is resolved and if any of the responses helped.
If you're still facing issues, feel free to reach out.
Thank you.
Hi @GaryAtGW ,
Just checking in to see if you query is resolved and if any responses were helpful.
Otherwise, feel free to reach out for further assistance.
Thank you.
Hi @GaryAtGW ,
Thanks for raising this in Microsoft Fabric Community.
The error occurs when one or more sources in the dataset are not fully bound in the service. Even if the folder path has been added in the gateway, the dataset still needs to have the folder source explicitly mapped under Gateway and Cloud Connections. Please confirm this mapping is in place.
The semantic model does not require a gateway, but it is good to verify the connection settings there as well. Ensuring both sources are correctly mapped under the dataset settings should resolve the missing connection details message.
For reference: Add or remove a gateway data source - Power BI | Microsoft Learn
Please reach out for further assistance.
Thank you.
Thanks @rohit1991 for your valuable guidance.
Hi @GaryAtGW
Could you please do this checklist end-to-end:
1. Confirm it’s a composite model (not Live)
2. Folder source (on-prem)
3. Upstream semantic model(s)
4. Your published dataset (the composite one)
5. Privacy levels
If policy blocks any of the above, try one of these workarounds:
Hello!
Thanks for your response, answers to your points below.
1. It doenst say live connection. When i mean live its a constantly updated data pushed out so I dont need to hit the refresh button
2. Its set as the server not as the i: drive. I cant edit the gateway but i can see the folder path is there using the server name pathway and its got the green online. when i manually refresh it loads any new files in the respective folders.
3. I have build permission on all models. They have the direct query allowed. Even the owner and publisher or the semantic models i connect to runs into the same issue.
4. Theres no fix now, all the models load data seperatly. Its when i connect both it errors.
5. All privacy i set to are organisational and where its prompted Autho2
I will have a look at the 2 seperate reports and I wonder if i make an online dashbaord i can return the rows with a common column.
Thank you
Gary
Hi @GaryAtGW
If you want me to pinpoint the exact miss
Share two screenshots from the Service:
That will make the gap obvious.
User | Count |
---|---|
66 | |
61 | |
47 | |
33 | |
32 |
User | Count |
---|---|
87 | |
72 | |
56 | |
49 | |
45 |