Видео

Exactly, an expert see's if the CAN do it, before asking if they NEED to do it 😅

Absolutely! I do show how to reduce the data labels for just min/max around the 9:40 mark. Start/End values are good ideas too, if you're going for that sparkline look. With anything it really boils down to what's most important for the users to look at :) It's why visual design is such a great combination of art and science 😁 I've found that screenshots of legends can end up being fuzzy and don't scale as well, making it more noticeable (to me) that it's an image, not a live rendering. But both work! Depending on the calc though, the visual container rendering could take a similar time. I ensure that any measure I use in the visual is cheap. Or even go as far as creating blank measures to use (hidden), so then there's 0 cost from the DAX perspective. ruclips.net/video/teX0hUqN370/видео.htmlsi=KXAtM2UwYfB-CrkF&t=578

Could you elaborate on what you mean by dynamic?

Heck yeah, thanks for that!

Glad it was helpful! The new features from the #PBICoreVisuals team is really making it easier too

Glad you liked it!

Some of my later videos in this series address that. Check the YT description for links to the follow up videos :)

@@HavensConsulting thanks a lot, i was kind of struggling here. The video is so helping. Thanks for the quicker response 😃

@@HavensConsulting i tried it but i got trouble getting the desired results, my 2023 and 2024 sales are located in different tables and i have connected those sales datas dates with calendar table. When i do this formula i am getting filtered only this year sales till date and last years disappear’s. How will i see last years sales from jan to till date along with current years. This is what i want. Need your assistance here 🥹.

Fully supported. Currently this is just a folder and formatting restructuring. No changes to the actual JSON code are being made, so backward compatibility for custom theme files will work :)

Awesome, the seem like they would work hand in hand but wanted to make sure! Thanks for verifying!

Not sure I'm following? Could you elaborate on the issue?

Interesting, i've never seen that! Might be worth filing a bug on Microsoft using the ? icon in the upper right for this one

Metric field definitions would be kept in the model layer. You could extract those via C# using Tabular Editor I'd figure :)

Glad it helped!

There aren't many tools for debugging specifically. Custom connectors are custom enough that outside of RUclips videos like this there aren't many official courses. More experts to reach out to contract when help is needed, since not a lot of people need to build them

My pleasure!

Thank you so much!

If you go to our Blog Files page you can download the PBIX for free and get the code from there :) www.havensconsulting.net/blog-files

Native queries have their own complexities, and by default break any ability for Power Query to fold on top of it (more below) ruclips.net/video/DWbh7xp08l0/видео.html It also relies on having a developer know SQL and SQL optimization techniques, which are all built into the query folding engine. Like with most things though, it depends. :)

Happy to help!

Great question! I'd recommend reaching out to SQLBI directly on this one for support on their tool :)

Not sure about this one, I tested again on a random PBIX I have with a custom visual (OKViz Sparkline), and getting the file from the inside zip and importing in another worked for me. What was the custom visual you were trying to extract?

Oh definitely. It works very well to show a before/after to any stakeholder, manager, or client when discussing results :)

It's the magic sauce of Power Query :). Transformations are translated from M (Power Query) to the source, and passed back for the source to transform (faster). Rather than Power BI downloading the unprocessed data, and doing it itself (slower). You can easily get a 5, 10, 20+ times performance increase when the source database does most the work. A quick google search would give you some helpful results like below on why it makes queries faster. www.reddit.com/r/PowerBI/comments/14strbb/what_does_folding_in_query_folding_means/ Also, to note,. Incremental refresh is explicitly advised NOT to use without folding. Because without folding you download the entire data before filtering to the relative period. Which is why when folding can't be confirmed with the engine, it gives a big warning that advises not to use incremental refresh. More below on that as well. learn.microsoft.com/en-us/power-bi/connect-data/incremental-refresh-overview

@@HavensConsulting Thank you for your explanation. Are you saying if I write "Select ProductID from Sales" myself in the Source dialog Advanced options, Power Query still loads all the data first, then executes my Select statement?

@@1yyymmmddd native queries (e.g. writing custom SQL Code in the statement box) will actually break any ability to query fold. So generally advised to not use that. It's advised to use the Power query actions to choose your columns, filter your rows, do your transformations. etc. More info about native query limitations below learn.microsoft.com/en-us/power-query/native-database-query

Lovely as well!

I used a DAX calculated column for that :) Window Key = SWITCH( TRUE(), '.Parameter - Dynamic Columns'[Parameter - Dynamic Windows Order] <= 2, 0, '.Parameter - Dynamic Columns'[Parameter - Dynamic Windows Order] <= 5, 1, '.Parameter - Dynamic Columns'[Parameter - Dynamic Windows Order] <= 8, 2 )

@@HavensConsulting Thank you so much! I'm trying to do something similar with a report I have, is there a reason why you used a different table for the window key, couldn't you just add directly the 1,2,3 of the month window size to the fields parameter table you already had?

You're so welcome!

In Fabric, so long as you have permissions, you can cross-query across Lakehouses/warehouses from a single SQL Endpoint. So you're right, my data is stored in the 100 Lakehouse, but I'm creating my new tables in the 200 Warehouse. I'm still able to query the 100 LH from the 200 WH using the single 200 connection string in my dbt profile. Although it's not an essential step, I also declared/aliased my source tables in a sources yml file so I could maintain lineage to the source tables. Hope that helps.

@@johnnyw5627 Great! I am also testing Fabric now with an Azure trial account. Do you think that I have enough permissions for this cross-query Lakehouse/warehouse scenario? So 100 is not a DWH but it is a Lakehouse! Mind blowing... Do you have a repo for this example we can check? Thanks Johnny!

Thank you for your replay.❤ Permissions.. hmmm, with free trial!!! This is really cool what you did there with 100 lakehouse and 200 warehouse... I am really curious to see you .profiles and dbt_project files to see how it is done! (Github?)

For folks asking, there's a repo here: github.com/GreyskullAnalytics/by-the-power-of-analyics-engineering

@@johnnyw5627 Thanks Johnny!

Thank ya! Though I try to avoid a "hack" or "trick" term, especially if it's uncovering a native hidden feature that doesn't break anything. Hacks to me would be more like layering two visuals to make it look like one visual, etc. Anything with a downside basically as a cost to the hack.

There's a video link in the description of this video that should solve that issue for you. Part 5 of this series :)

@@HavensConsulting Thank you, that worked.