interesting links
7383 TopicsMigrating Reports from Tableau to Power BI
HI Team, We are plannig to migrate report from Tableau to Power BI from April 1st. When, i check the previous discussion on any helping tools to migrate reports from tableau to power bi. First, currently do we have any tools to migrate report? Second, any alternative suggetion to to reduce the efforts to migrtae 100 dashboards. I appreciate the help Thank you in advance!Solved37KViews2likes19CommentsArchivos de Adobe incrustados en la aplicación powerbi
En la aplicación de powerbi tenía publicados unos vínculos que hacían referencia a archivos adobe y no tenía ningún problema, los podía visualizar correctamente en la misma página de la aplicación, pero ahora me está apareciendo el error que adjunto y no sé si es problema de la aplicación, del adobe o de permisos de mi institución. Alguien tiene alguna sugerencia o idea?75Views0likes3CommentsLooking for Ideas to Improve Power BI Filtering Pane Visibility
Hi everyone, I'm looking for ideas and best practices to make the Power BI filter pane more user-friendly. We're currently using the default filter pane, but users often find it difficult to see which filters are selected, especially when multiple filters are applied. Since moving filters onto the report page isn't an option, I'm interested in ways to make active selections more visible through colors, custom designs, or other UX approaches. Any suggestions, examples, or screenshots would be greatly appreciated. Thanks!Solved51Views2likes1CommentUnderstanding Power BI B2B Licensing and Embedded Scenarios
Understanding Power BI B2B Licensing and Embedded Scenarios I'm trying to understand how Power BI licensing, Microsoft Entra B2B, and Power BI Embedded work together. I'd appreciate clarification on the following scenarios. Scenario Tenant A owns the Microsoft Entra tenant, Power BI tenant, workspace, semantic model, reports, dashboards, and apps. [email protected] is an external user. Question 1 – B2B Guest + Pro Workspace Assume [email protected] is invited as a B2B guest into Tenant A. The workspace is a Power BI Pro workspace (not Premium Capacity or Fabric Capacity). What are the exact checks Power BI performs before allowing access? Are the checks performed in this order? User authentication B2B guest validation Tenant settings Power BI license validation Workspace/App permissions Semantic model permissions RLS Is this the complete authorization flow, or are there additional checks? Question 2 – Cross-Tenant Licensing If the external user has a Power BI Pro license assigned in their home tenant (Tenant B): Can that license be used to access reports hosted in Tenant A? If yes, how does Microsoft validate the license across tenants? Does the guest require a Pro license assigned in Tenant A, or is the home tenant license sufficient? Question 3 – User Owns Data vs App Owns Data I'm trying to understand the architectural difference. User Owns Data Who authenticates to Power BI? Does Power BI evaluate the end user's identity? Is a Pro/PPU license required? What happens if the user has no Power BI license? App Owns Data Who authenticates to Power BI? Does Power BI evaluate the end user's identity or only the application/service principal? Why is Embedded Capacity required? Why doesn't the end user need a Pro license? Question 4 – Embedded with Existing B2B Users Suppose the external user is already a B2B guest in Tenant A. Instead of accessing reports through Power BI Service, they access them through a secure web application using Power BI Embedded. Is this a supported architecture? Should this use User Owns Data or App Owns Data? Which approach is recommended and why? Question 5 – Recommended Architecture For each of the following scenarios, what is the recommended architecture and licensing model? Internal employees External partners (B2B guests) Customers using a secure web portal Public-facing dashboards When should I choose: Power BI Service B2B Guest Access Power BI Embedded (User Owns Data) Power BI Embedded (App Owns Data) Publish to Web I'm looking for the recommended architecture along with the licensing requirements for each scenario. amitchandak Ashish_Mathur super229Views2likes9CommentsValidation of my understanding of Fabric Semantic Models, Power BI Desktop, and Workspace Scenarios.
Validation of Microsoft Fabric Semantic Model Architecture, Connection Modes, and Power BI Desktop Behavior Hi everyone, I've been exploring different Microsoft Fabric and Power BI integration scenarios and would like to validate my understanding. I'd also appreciate clarification on a few concepts related to Semantic Models, connection modes, and Power BI Desktop. 1. End-to-End Fabric Architecture Data Sources ↓ Fabric Lakehouse / Warehouse ↓ Centralized Semantic Model ↓ Power BI Reports / Paginated Reports My understanding is: Data is ingested into Fabric Lakehouse or Warehouse. A centralized Semantic Model is created on top of the data. Multiple reports can consume the same Semantic Model. This is the recommended enterprise architecture for governance, scalability, and reusable business logic. Is this correct? 2. Fabric Semantic Model → Power BI Desktop Fabric Semantic Model ↓ Power BI Desktop ↓ Report My understanding is: Power BI Desktop connects to the published Semantic Model using a Live Connection. Reports can be developed in Power BI Desktop. The Semantic Model itself cannot be modified because it is centrally managed in Fabric. However, whenever I connect to a Fabric Semantic Model from Power BI Desktop, Desktop opens in Semantic Model editing mode, and I don't see the Report View. My questions are: Is this expected behavior? Why is Report View not available? Is there a way to create reports directly from the same Power BI Desktop session after connecting to a Fabric Semantic Model, or is this by design? What is the recommended workflow for report developers in this scenario? 3. Power BI Pro Workspace and Fabric My understanding is: A standard Power BI Pro workspace cannot host Fabric artifacts such as Lakehouses, Warehouses, Notebooks, or Pipelines because they require Fabric capacity. However, a Pro workspace can consume an existing Semantic Model published from a Fabric workspace (subject to permissions and licensing). Reports can then be created using that Semantic Model. Is this correct? 4. Connecting Power BI Desktop to a Fabric Warehouse I believe there are two approaches. Approach 1 – Semantic Model Development Fabric Warehouse Tables ↓ Semantic Model ↓ Power BI Desktop Used for Semantic Model development. Opens in Semantic Model editing mode. Report View is not available. Approach 2 – Direct Connection Fabric Warehouse Tables / SQL Objects (Tables, Views, etc.) ↓ Power BI Desktop ↓ Semantic Model ↓ Report Connect directly to the Fabric Warehouse. Use Warehouse tables or SQL objects such as views. Power BI Desktop provides the normal report authoring experience. Semantic Model and reports are developed together. Is this understanding correct? 5. Connection Modes within a Fabric Semantic Model I'm also trying to understand how the following storage/connection modes work in Fabric Semantic Models. Import DirectQuery Direct Lake My questions are: Can all three connection modes be used when creating a Semantic Model in Fabric? What are the recommended scenarios for each mode? Are there any limitations depending on whether the Semantic Model is built from a Lakehouse or a Warehouse? Can these modes be mixed within a single Semantic Model? 6. Refresh Behavior and Data Pipeline I'd also like to understand how Semantic Model refresh works in a complete Microsoft Fabric solution. Assuming data is loaded into a Lakehouse or Warehouse through any Fabric ingestion mechanism, such as: Dataflow Gen2 Notebooks Pipelines Mirroring Shortcuts Other supported Fabric ingestion methods My understanding is that all of these eventually populate the Lakehouse or Warehouse, which is then consumed by the Semantic Model. My questions are: Is this understanding correct? Does the Semantic Model refresh behavior remain the same regardless of whether the data was loaded using Dataflow Gen2, Notebooks, Pipelines, or any other Fabric ingestion process? How does Semantic Model refresh work for each storage mode: Import DirectQuery Direct Lake Is a scheduled Semantic Model refresh always required, or does it depend on the storage mode? For Direct Lake, when new data is written into the Lakehouse or Warehouse, does the Semantic Model automatically reflect those changes, or is some form of model refresh still required? Are there any best practices for orchestrating data refresh and Semantic Model refresh within Microsoft Fabric? 7. Cross-Workspace Scenarios Is my understanding correct? Fabric Workspace Semantic Model → Fabric Report → Supported Fabric Workspace Semantic Model → Power BI Desktop Report (Live Connection) → Supported Power BI Workspace Semantic Model → Fabric Report → Supported Power BI Workspace Semantic Model → Power BI Report → Supported 8. Semantic Model Terminology One area I'm still trying to clarify. Is there technically any difference between a Fabric Semantic Model and a Power BI Semantic Model, or are they actually the same Semantic Model artifact, with the only difference being where they are created or hosted? I'd appreciate any corrections or clarifications. My goal is to build a solid conceptual understanding of Microsoft Fabric architecture, Semantic Models, and the recommended enterprise development workflow. Thank you!121Views0likes4CommentsPower BI Data load , Refresh from Salesforce is Taking Too Long
Hi Community, I'm currently working on a Power BI project where the data source is Salesforce. The dataset currently consists of only 3 Salesforce objects, with a total of approximately 5 million (50 lakh) rows. The data volume is expected to grow over time. To optimize refresh performance, I've already implemented the following: Created partitions using Tabular Editor. Configured monthly incremental refresh. Processing the partitions using SQL Server Management Studio (SSMS). However, the refresh process is still taking much longer than expected. Even processing only the latest monthly partition requires a significant amount of time. I'm trying to understand what could be causing this performance issue. Here are a few details about my setup: Data Source: Salesforce Objects Number of Tables: 3 Current Row Count: ~5 million Storage Mode: Import Partitioning: Monthly partitions created using Tabular Editor Processing: SSMS (XMLA endpoint) Expected Future Growth: Data volume will continue to increase. I would appreciate your guidance on the following questions: Is this refresh duration expected when using Salesforce as the source? Are there any known limitations or performance bottlenecks with Salesforce connectors? What factors should I investigate (network latency, Salesforce API limits, query folding, transformations, etc.)? Are there any best practices for improving refresh performance with Salesforce datasets of this size? Is monthly partitioning sufficient, or would a different partitioning strategy (weekly/daily) improve performance? Has anyone worked with Salesforce datasets of similar size, and what refresh times are considered reasonable? Any recommendations, troubleshooting steps, or best practices would be greatly appreciated. Thank you!Solved402Views1like9CommentsPremium_ASWL_Error
Hi, The reports were working fine for a couple of months, but yesterday I suddenly got this error below. The reports were not showing in both the Power BI Service and Embedded application. After we re-entered the credentials on the embedded application, this error went. When we re entered credential server name we give without the port number. What was the reason this issue occurred suddenly? Data source error: {"error":{"code":"Premium_ASWL_Error","pbi.error":{"code":"Premium_ASWL_Error","parameters":{},"details":[{"code":"Premium_ASWL_Error_Details_Label","detail":{"type":1,"value":"We cannot refresh this dataset because the dataset contains calculated tables or calculated columns based on data from a Single Sign-on (SSO)-enabled Direct Query data source. Please configure the dataset to use an explicit connection with granular access control to access this data source and then try again."}}],"exceptionCulprit":1}}} Cluster URI: WABI-US-EAST2-redirect.analysis.windows.net Activity ID: a13987f1-b35a-4c58-b758-96352945dea4Solved242Views0likes5Comments