Amazing 42 minutes of my time! Thank you for putting this video up. I am also struggling in trying to understand on how to integrate all the latest features in PBI. This end to end project of yours is just an eye opener on what MS Fabric can do.
Great video! One of my main concerns recently has been migrating from my existing semantic models using import mode to new one's using directlake. I was worried I would need to rewrite all my relationships, measures, roles, etc. Looks like Tabular Editor could save me the headache.
Now I see a serious problem with continuous improvement in PBI , fabric lake house workflows etc . I feel like I’ve been using using a beta version of powerbi service all these years ,MS should put a hold onto this at some point .It’s hard to catch up , I got 1k+ dataflows n hundreds of shared datasets , I’m hesitant to adopt new fabric items while leaving behind the existing Gen2 content. Balancing innovation with practical implementation is essential.. It’s gonna create a lot a chaos with user base and of course administration . I think MS should take a break n let us sink in
That's the struggle, right? A good product leads to good amounts of development. Good amounts of development take time to migrate or upgrade. Yet at the same time, as technology changes and evolves, a good product needs to do the same thing. The question is, what is your strategy for managing this change with existing code bases. Let me think about doing a video on how to deal with this. Good news, MSFT is VERY slow at deprecating things, and for providing a path from the old to the new to make it easier to transition. Now, they are not perfect (we all have nightmare stories where they fell short), but they do a fairly good job.
@@ChrisWagnerDatagod yes, MSFT invests in components for its best-selling solutions, a clear example of PBI, which is why we have versions every x month in the year, while its B.D is still with the 2022 version because the focus is more on the ETL layer side in solutions of data.
Amazing 42 minutes of my time! Thank you for putting this video up. I am also struggling in trying to understand on how to integrate all the latest features in PBI. This end to end project of yours is just an eye opener on what MS Fabric can do.
So glad that you enjoyed it and found it beneficial. Stay tuned for more!
Great video! One of my main concerns recently has been migrating from my existing semantic models using import mode to new one's using directlake. I was worried I would need to rewrite all my relationships, measures, roles, etc. Looks like Tabular Editor could save me the headache.
Oh 100% Tabular editor makes it MUCH easier to do the migration. It's not point and click, but it's leagues better than what I feared as well.
Now I see a serious problem with continuous improvement in PBI , fabric lake house workflows etc . I feel like I’ve been using using a beta version of powerbi service all these years ,MS should put a hold onto this at some point .It’s hard to catch up , I got 1k+ dataflows n hundreds of shared datasets , I’m hesitant to adopt new fabric items while leaving behind the existing Gen2 content. Balancing innovation with practical implementation is essential.. It’s gonna create a lot a chaos with user base and of course administration . I think MS should take a break n let us sink in
That's the struggle, right? A good product leads to good amounts of development. Good amounts of development take time to migrate or upgrade. Yet at the same time, as technology changes and evolves, a good product needs to do the same thing. The question is, what is your strategy for managing this change with existing code bases. Let me think about doing a video on how to deal with this. Good news, MSFT is VERY slow at deprecating things, and for providing a path from the old to the new to make it easier to transition. Now, they are not perfect (we all have nightmare stories where they fell short), but they do a fairly good job.
@@ChrisWagnerDatagod yes, MSFT invests in components for its best-selling solutions, a clear example of PBI, which is why we have versions every x month in the year, while its B.D is still with the 2022 version because the focus is more on the ETL layer side in solutions of data.