Power BI for Business Professionals - WK20 - The untold problems with UDF's скачать в хорошем качестве

Power BI for Business Professionals - WK20 - The untold problems with UDF's

UDFs break your development process. As things stand, with no clear path for when we can expect these to move out of preview, it is clear that while these could be amazing, we simply cannot use them. So, how can Microsoft get meaningful test data? Overall, the groundbreaking feature is (at the time of shooting) broken and unusable in any organisation of meaningful size. Shape Maps, a visual used by many organisations, has been in preview for 5+ years. UDF's are still in preview; however, they are completely absent from the product roadmap. This makes it impossible to plan and determine how far you should take your learning and how to prepare your business for the new feature. Combine that with some real deal breakers you see in the video, and the result is a great feature that can't be used or explored. Let us know your opinion in the comments. Check out the roadmap for yourself: https://roadmap.fabric.microsoft.com/... Microsoft's UDF Documentation: https://learn.microsoft.com/en-gb/dax... In answer to those of you saying, "You shouldn't be using Preview features in Production", that can only work with a proper roadmap. If you are putting major platform changes into preview that are not on the roadmap, you are doing your clients a disservice. We have also been present in enough meetings with Microsoft where clients have been warned about similar things in public previews, but given the "Go ahead into production, but do so with your eyes open" style of warning. UDFs in their current state change the Power BI development model, and they significantly impact the Fabric Adoption Framework, so clarity is needed. Without that clarity, the only advice can be "do not touch". Finally, we look at how our demo semantic model has grown in business importance throughout this series. It now has 12 reports across 6 workspaces. This is tiny compared to what we see in real-world enterprise semantic models, where 100+ reports and connections to 10+ workspaces are not uncommon. This is why changes to your development cycles are not trivial. It is nearly impossible to have a team centrally do all the work for that many reports and teams, especailly considering that potentially any of those reports could have secondary measures (DAX statements unique to them), the process of promotion of those is core to success but that feature must be there, or you risk divergance as it is too difficult to get the results into Power BI meaning people go back to extracting data and producing content in Excel. ========== 🍵 ========== Support the channel, buy me a coffee https://buymeacoffee.com/rossj ========== 📊 ========== View the main reports we use in this series. NECA pakruns - https://app.powerbi.com/view?r=eyJrIj... New Report - Disconnected Slicers combined with UDF https://app.powerbi.com/view?r=eyJrIj... ========== 🤝 ========== Book your Consultancy Introductory Call https://outlook.office365.com/owa/cal... ========== 🍵 ========== Support us: https://geordieintelligence.co.uk/sup... #PowerBI #PowerBITraining #PowerBIDeveloper #PowerPlatform #udf #dax 00:00 - Introduction 02:35 - New publicly shared report - how to use it 06:10 - The problems 07:40 - No visibility of the UDF from traditional tools 08:30 - No access to call the function from Secondary Reports 19:30 - Quick note - Semantic model value increases 22:15 - Final thoughts