Design principles

[Gill_SRAM]

Hi everyone,

Would love to hear your views on a new dashboard I am designing.

We use Bex queries via oData.  I am pulling in five years worth of sales data and a faily high level.   For one chart in my dashboard I am breaking out two years worth of Sales Actual - Plan and Prior Year values by month.  I have some transformations to do on the data to convert the Calendar Year/Month to a 2 digit field called Month and then I change the month numbers to month names and plot the output.

Should I bring in a second 0data source (which would be the same BEx query but only selecting a narrow subset of data in my Select URL statement) that only contains that two years worth of data I need or would I stick with the one data source and transofrm all the data.  

I'm wondering about best practise here in terms of speed/performance in that there is no point in having the system transform the Calendar Year/Month field to a month name if I don't need it.

Thanks for reading this far 🙂

Gill 

[amitchandak · Accepted solution]

@Gill_SRAM ,

refer

https://maqsoftware.com/expertise/powerbi/power-bi-best-practices

https://docs.microsoft.com/en-us/power-bi/guidance/power-bi-optimization

https://www.c-sharpcorner.com/article/power-bi-best-practices-part-1/

https://www.knowledgehut.com/blog/business-intelligence-and-visualization/power-bi-best-practices

https://community.powerbi.com/t5/MBAS-Gallery/Microsoft-Power-BI-The-Do-s-and-Don-ts-of-Power-BI-Rel...

https://community.powerbi.com/t5/MBAS-Gallery/Microsoft-Power-BI-My-Power-BI-report-is-slow-What-sho...