Forum Discussion
Help Me Optimize This Weird API-Based Near Real-Time Power BI Embed Refresh Solution I've Created
Hi Mahhin_Shahzad1 ,
It's great to see the progress you've made so far. Partitioning using XMLA appears to be a logical next step, and while I haven't implemented it directly, I've seen several sources indicate it works effectively with surrogate keys for non-time-based incremental refresh scenarios.You may find this Microsoft Learn article useful:
Incremental refresh and XMLA endpoint in Power BIBased on my research, workspace isolation and embedding through the JS API can support client-specific branding and access control, which could complement your XMLA approach.
Are you considering managing dataset versions for each client, or will you use a shared dataset with dynamic partitioning rules? This decision may influence your refresh and isolation strategies.
1. Maybe use a budgeting/forecasting tool like Anaplan?
2. Push datasets are a dying breed. Microsoft already tried to kill it once and they will try again. Also, they are live connections only.
3. It is not clear if/how/when Fabric will work with embedded scenarios
4. You can do manual partition management via XMLA, and the partition rules don't have to be time based.
Actually, we are a forecasting company ourselves, similar to Anaplan, and I had to build a robust multi-client architecture.
The other suggestions were helpful — especially the partitioning via XMLA endpoint. I’m going to look into that further.
Actually, we are a forecasting company ourselves, similar to Anaplan, and I had to build a robust multi-client architecture.
The other suggestions were helpful — especially the partitioning via XMLA endpoint. I’m going to look into that further.
Hi Mahhin_Shahzad1 ,
It's great to see the progress you've made so far. Partitioning using XMLA appears to be a logical next step, and while I haven't implemented it directly, I've seen several sources indicate it works effectively with surrogate keys for non-time-based incremental refresh scenarios.You may find this Microsoft Learn article useful:
Incremental refresh and XMLA endpoint in Power BIBased on my research, workspace isolation and embedding through the JS API can support client-specific branding and access control, which could complement your XMLA approach.
Are you considering managing dataset versions for each client, or will you use a shared dataset with dynamic partitioning rules? This decision may influence your refresh and isolation strategies.
