Before Fabric, I felt on top of everything Power BI. But now, with the expansive updates from Fabric, it's like trying to drink from a fire hose-there’s just too much to keep up with! Thank you for highlighting this, It comforts me to see that I'm not the only one feeling this way.
Keeping up is my full time job. Not going to lie, its hard. It would be SUPER helpful if you defined (formally) the roles in Fabric. Fabric analyst, fabric developer, fabric engineer, data scientist, Real time engineer, Fabric Administrator. or whatever. Then tag the updates with the role and the technology eg Fabric engineer, Powershell with XMLA endpoints. That way without having to read them all we can find the ones relevant to our roles without having to waste time on some niche use case we are never going to use. It would also be VERY helpful if each blog post has a clear use case tagged onto the end. So many of them are chatty, "This is awesome", "you can do stuff" but by the end I'm struggling to see what the use case for the feature is. I'm not saying all the blogs should come out with the charm of a paginated report but some defined structure with searchable tags relating to technology and roles and very clear use cases at the bottom of each blog saying you should use it when, this allows you to do x. Not just this obscure function now supports an even more obscure use case. The tags will be invaluable to those who are new to fabric, so they can search the most relevant posts to thier role. I've been running fast for nearly 10 years and it's only getting faster.
Working with Power BI since 2016, I felt so overwhelmed with the monthly updates and I thought I have to implement every flashing update to my existing reports. However, I now keep all my Power BI reports with strong bases: a good model, clean DAX measures publishing and creating Apps for the report consumption, in other words, understanding the architecture is the key. Knowing the new monthly updates is important to me only to know that some roadblocks are solved and I can offer a solution. By the way of conclusion, as Adam said, stick with the plan.
2017 here. And totally agree. If the plan in your organizations is to use powerbi for reporting, use it for reporting. Apps are a cool way to centralize distribution, and reports using connections to core datasets is a must. But this means you have to have a plan for it, and understand your data architecture and pipelines. Fabric makes this last step an absolute mess, but it CAN be simple if you dont let people chase the buzzwords (and by people I mean the know-it-alls and finance-bros from your typical commercial and finance departments)
Thank you, Adam, for this short and impactful message! It’s impressive to see how fast Fabric’s environment is evolving, and I wish I used more of my time to keep updated. I’m getting better at it, but this also helps putting things under a more focused lens: priorities! 🙏🏻
Thank you!!! Finally someone to say it loud. It is recommended to be aware of all the updates, but there is absolutely no necessity to implement all of them, right here, right now. As clients would like.
Thanks, Patrick. I am more annoyed by Microsoft's policy to push everyone to adopt Fabric and not give the option to keep just Power BI. It is so disturbing. We have huge Azure subscriptions and snowflakes, and so on. We already use Microsoft a lot, but not enough for them. They have to push for more. I am thinking of already moving to other competitors' tools just to protest for this move. I agree with you, Fabric is not answer to everything to everyone and even maybe only Power BI is answer for some people. But Microsoft need to understand this.
Super important topic. For me, it's important to realise fabric is too big to be an expert on everything. I now specialize, and that makes it more manageable.
Great study here Guy in a cube , thanks a lot Yes It's sometime painful to learn each month new releases But I wan to distinguish "abnormal" new features because Microsoft delivered initially a "semifinished " product ...from "normal" ones due to product improvement innovation
Thank you for another great video! I have a weird problem maybe you could take a look. I have a Power BI report where I create/test measures and visuals. In one of the visuals, I put together everything I wanted to show and published to Power BI Service. Then I pasted the visual in a report connecting to the published Power BI dataset. All measures showing correctly in the visual except one - which shows blank. I could not figured why. Is there any situation where the measure will show blank values? Greatly appreciate if you could take a look and maybe do a video about it!
Thanks for considering this topic, which is probably relevant for most of us. Our company decided to use azure synapse 2 years ago, but we just started implementing (decision take a long time for our company) and now that fabric is here we feel like we are forced to work on implementing on a platform that is doomed to phase out soon. What do you think about that?
I’m in a similar boat. I built an end to end solution for a small business unit in synapse to prove it would work well for us in replacing our main dwh. And a week after I finished Microsoft announced fabric. I’m ignoring it for now - I’m going to proceed with the synapse build but learn fabric in my spare time. Perhaps we will use it in a couple of years - but for now it’s not even a finished product.
Most of updates these days are useless with some exceptions. I honestly do not understand why Microsoft is rushing it instead of focusing on bugs. I also see that some useful features are silently removed without notice like the option to forbid PBI to set relationships automaticaly (which on the other hand never worked properly). I only do every update because they fix some bugs silently without mentioning it.
Thanks for giving voice to this. I get so overwhelmed with all that comes out. I always feel like I can never get in front of it.
Before Fabric, I felt on top of everything Power BI. But now, with the expansive updates from Fabric, it's like trying to drink from a fire hose-there’s just too much to keep up with!
Thank you for highlighting this, It comforts me to see that I'm not the only one feeling this way.
Keeping up is my full time job. Not going to lie, its hard. It would be SUPER helpful if you defined (formally) the roles in Fabric. Fabric analyst, fabric developer, fabric engineer, data scientist, Real time engineer, Fabric Administrator. or whatever. Then tag the updates with the role and the technology eg Fabric engineer, Powershell with XMLA endpoints. That way without having to read them all we can find the ones relevant to our roles without having to waste time on some niche use case we are never going to use. It would also be VERY helpful if each blog post has a clear use case tagged onto the end. So many of them are chatty, "This is awesome", "you can do stuff" but by the end I'm struggling to see what the use case for the feature is. I'm not saying all the blogs should come out with the charm of a paginated report but some defined structure with searchable tags relating to technology and roles and very clear use cases at the bottom of each blog saying you should use it when, this allows you to do x. Not just this obscure function now supports an even more obscure use case. The tags will be invaluable to those who are new to fabric, so they can search the most relevant posts to thier role. I've been running fast for nearly 10 years and it's only getting faster.
Working with Power BI since 2016, I felt so overwhelmed with the monthly updates and I thought I have to implement every flashing update to my existing reports. However, I now keep all my Power BI reports with strong bases: a good model, clean DAX measures publishing and creating Apps for the report consumption, in other words, understanding the architecture is the key. Knowing the new monthly updates is important to me only to know that some roadblocks are solved and I can offer a solution.
By the way of conclusion, as Adam said, stick with the plan.
2017 here. And totally agree. If the plan in your organizations is to use powerbi for reporting, use it for reporting. Apps are a cool way to centralize distribution, and reports using connections to core datasets is a must. But this means you have to have a plan for it, and understand your data architecture and pipelines. Fabric makes this last step an absolute mess, but it CAN be simple if you dont let people chase the buzzwords (and by people I mean the know-it-alls and finance-bros from your typical commercial and finance departments)
Thanks Patrick! You hit a nerve. Iam more and more overwhelmed by all the new features in the Data Platform Cosmos and hardly can keep pace.
Thank you, Adam, for this short and impactful message! It’s impressive to see how fast Fabric’s environment is evolving, and I wish I used more of my time to keep updated. I’m getting better at it, but this also helps putting things under a more focused lens: priorities! 🙏🏻
Thank you!!! Finally someone to say it loud.
It is recommended to be aware of all the updates, but there is absolutely no necessity to implement all of them, right here, right now.
As clients would like.
Thanks, Patrick. I am more annoyed by Microsoft's policy to push everyone to adopt Fabric and not give the option to keep just Power BI. It is so disturbing. We have huge Azure subscriptions and snowflakes, and so on. We already use Microsoft a lot, but not enough for them. They have to push for more. I am thinking of already moving to other competitors' tools just to protest for this move.
I agree with you, Fabric is not answer to everything to everyone and even maybe only Power BI is answer for some people. But Microsoft need to understand this.
Great points, Adam. And if you see anyone on your teams struggling with this, help them by reducing the pressure. Never be the cause of stress.
Super important topic. For me, it's important to realise fabric is too big to be an expert on everything. I now specialize, and that makes it more manageable.
Great study here Guy in a cube , thanks a lot
Yes It's sometime painful to learn each month new releases
But I wan to distinguish "abnormal" new features because Microsoft delivered initially a "semifinished " product
...from "normal" ones due to product improvement innovation
Thank you for another great video!
I have a weird problem maybe you could take a look. I have a Power BI report where I create/test measures and visuals. In one of the visuals, I put together everything I wanted to show and published to Power BI Service. Then I pasted the visual in a report connecting to the published Power BI dataset. All measures showing correctly in the visual except one - which shows blank. I could not figured why. Is there any situation where the measure will show blank values?
Greatly appreciate if you could take a look and maybe do a video about it!
Thank you for this much-needed message!
Cool. An eye opener , instead of rushing through to catch the shiny icecream van.
Thanks for considering this topic, which is probably relevant for most of us.
Our company decided to use azure synapse 2 years ago, but we just started implementing (decision take a long time for our company) and now that fabric is here we feel like we are forced to work on implementing on a platform that is doomed to phase out soon. What do you think about that?
I’m in a similar boat. I built an end to end solution for a small business unit in synapse to prove it would work well for us in replacing our main dwh. And a week after I finished Microsoft announced fabric. I’m ignoring it for now - I’m going to proceed with the synapse build but learn fabric in my spare time. Perhaps we will use it in a couple of years - but for now it’s not even a finished product.
We are also going forward with our synapse framework, but try to keep up with fabric along the way.
I still don't understand Fabric.
You guys!!! ❤❤❤
Sage advice, my Power BI guru!🥰
my power bi power automate is not loading when I want to edit , online or desktop version. Is there a fix?
Oh the irony of updates in light of the Crowdstrike debacle
So true!
Most of updates these days are useless with some exceptions. I honestly do not understand why Microsoft is rushing it instead of focusing on bugs. I also see that some useful features are silently removed without notice like the option to forbid PBI to set relationships automaticaly (which on the other hand never worked properly). I only do every update because they fix some bugs silently without mentioning it.
I cannot be the only one who thinks there aren't enough updates?! 😳
I've worked for 20 years in BI and data analytics , I just want to quit now ! It's all cr@p
Focus 🎯
I like to work on no code solutions and platforms
Microsoft only makes money from shiny new product features. I would say 80% of Fabric users don't even need the product, and are wasting their money.
Guys at databricks is doing too much; sometimes I feel it’s so overrated
Bring back on prem...
@@gavinbroughton it's only a question of time.. 😆
what changed?
Report Servers are still a thing...