But, as a best practice, use the myorg alias and specify the tenant ID together with the app ID in the User ID parameter. Power BI can then locate the service principal in the correct tenant. However, in this case, you must replace the myorg alias in the data source URL with the actual tenant ID. It's also valid to specify the app ID without the tenant ID. Make sure you specify the tenant ID together with the app ID using the correct format. For service principals, make sure you specify the tenant ID together with the app ID using the format then try again." "We cannot connect to the dataset due to incomplete account information. To use a service principal, be sure to specify the application identity information in the connection string as:ĭata Source=powerbi:///v1.0/myorg/Contoso Initial Catalog=PowerBI_Dataset User you receive the following error: Keep in mind the service principal requires the same level of access permissions at the workspace or dataset level as regular users. If you've enabled tenant settings to allow service principals to use Power BI APIs, as described in Enable service principals, you can connect to an XMLA endpoint by using a service principal. Also, be sure to read the section Connection requirements for helpful tips and information about current XMLA connectivity limitations. To learn more, see Connecting to a Premium workspace. Establishing a client connectionĪfter enabling the XMLA endpoint, it's a good idea to test connectivity to a workspace on the capacity. This setting is also required for the Analyze in Excel feature. Keep in-mind, you must also enable the tenant-level Export data setting in the Power BI Admin Portal. For example, upgrading from an A1 to an A3 capacity solves this configuration issue without having to disable Dataflows. Limit the memory consumption of other services on the capacity, such as Dataflows, to 40% or less, or disable an unnecessary service completely.The error states "There was an issue with your workload settings. On smaller capacities, such as an A1 capacity with only 2.5 GB of memory, you might encounter an error in Capacity settings when trying to set the XMLA Endpoint to Read/Write and then selecting Apply. The XMLA endpoint can be enabled on both Power BI Premium, Premium Per User, and Power BI Embedded capacities. Other Power BI troubleshooting guides, such as Troubleshoot gateways - Power BI and Troubleshooting Analyze in Excel, can also be helpful. Most common XMLA endpoint use cases are covered there. Before you beginīefore troubleshooting an XMLA endpoint scenario, be sure to review the basics covered in Dataset connectivity with the XMLA endpoint. However, some differences around Power BI-specific dependencies apply. Because of this, XMLA endpoint troubleshooting is much the same as troubleshooting a typical Analysis Services connection. XMLA endpoints in Power BI rely on the native Analysis Services communication protocol for access to Power BI datasets.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |