Where's your date dimension?
Without date dimension table, you can't use time intelligence functions. When you do, you'll get unexpected results.
If you had date dimension, it would simply be...
=CALCULATE(([Target1 Customers]),SAMEPERIODLASTYEAR(DateTable[DateColumn]))
Also... you have non...
Without knowing your data structure, and without sample to work with... bit hard to give you specific help.
Try following article below, if you can't share your sample file.
https://blog.finance-bi.com/power-bi-cohort-analysis/
You can't. Since you have all fields in Row fields. Child field can only be sorted within context of parent field.
Meaning Expiry / Review Date will only sort within each parent ID / License field.
Looking at your source data of Pivot Table, "Lookuptable", and how your Pivots are structured...
COUNTA() is DAX function. But since DAX measure only allows for single value to be returned, you need to supply it context for it to be evaluated in.
Hence, suggestion to add Pivot Table or Matrix visual.
That really shouldn't be done in DAX. But in PowerQuery M code stage or before.
Easiest thing to do is remove duplicate operation in PQ stage.
But if you don't want to remove and just identify duplicate values in a column...
Just use pivot table / matrix visual. Depending on your tool.
Column...
Can't give you definitive answer without knowing your data model structure.
But you can just create OLAP based pivot table. Then go to PivotTable Analyze ribbon. Find OLAP Tools -> Convert to Formula.
That will give you the formula needed for the result.
Load data to PowerQuery. Then enter Query editor.
Click on pull down menu beside column name.
Select Date/Time Filters and then "Custom Filter".
Then select "Advanced" and set OrderDate "AND" City criteria.
NOTE: This is just example of how to do it. Since I wasn't exactly sure what end...
Without knowing what value is assigned to "WhereClause" variable when the error is thrown, hard to help you.
That error message is standard syntax error message from db side.
I suspect, there is invalid character or something else that's causing it, held in "WhereClause".
For Transform. You need to click on the Content column to expand the content.
This is more useful when you don't want to combine all files within given folder. Or you want to apply different transformation steps to files in given folder. Since you can use initial query as reference, or apply...
You are out of luck. I'm afraid.
To avoid this, I generally recommend using Top 1000 etc in your query (or using filter in PQ). Once you are satisfied with the model structure and performance. You can save a backup copy as is with limited data and then bring in complete data required.
Depends. More context and data structure sample are needed to give you guidance.
SSRS isn't necessary in this case. Unless you are dealing with 10GB + of data (assuming Pro subscription). PowerBI is more flexible in terms of data source and will be easier to develop for and manage rather than...
Few things you can try.
1. Incremental load
2. Set data load from db to occur only on schedule and during off peak hours
3. Split data into smaller chunks and publish in separate reports
Once data is loaded to the model. Returning result from within model is near instantaneous.
How and where it's used matters in DAX. Is it a measure? Calculated column?
I'd recommend uploading sample data model that demonstrates your issue. As well as sample/explanation of what the end result should look like.
It really depends.
Ex: If I have list of cities in North America and corresponding data.
I'll add country, province/state and region/county columns to dimension table. This allows me to first filter by country, then by province etc. Each subsequent slicer is already filtered by previous. So in...
It's possible. But you will need to set up bookmark for your visual.
Overview of bookmarks in Power BI service reports - Power BI | Microsoft Learn
It won't be dynamic. Personally I prefer to keep slicer option to be less than 12 or so. I use custom grouping etc within data model and build...
Oh by the way. Issue isn't with your measure. But how you constructed your visiual.
"Forename" in your visual is actually column from Contact. Not a measure. So based on other fields in the visual. It's filtered to the context that matches (i.e. Associated Contact Forename). You need separate...