Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
I have two custom connectors (both based on Web.Contents, not ODBC), one of which gets a list of entities, and the other one searches for that entity in an on prem site.
When I do this, I get a "Connection" dialog box pop up for each unique entity searched for (the box that just has the name of the data source accross the top, anonymous auth, and the two buttons, connect and cancel).
Is there a way to tell PBI that even though MyCustomConnector(entity1) and MyCustomConnector(entity2) are different calls, there should only be one DataSource?
Is that the same as edit permissions there, and set to public, or is it something else?
Is there a way to get PBI to accept that the "resource" that is being hit is the same even if the args to the function are different?
Check the scope of your data connection(s) and correct it to tie the credentials to the highest possible level.
How do I do that? It is implicit auth, there aren't credentials to tie.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 6 | |
| 3 | |
| 3 | |
| 3 | |
| 2 |