Performance of Report Builder Validation of Parameterized DAX Queries

Please vote this to fix what we perceive as the largest issue with Report Builder

There are large issues with Report Builder Parameterized DAX queries

Even with simple and fast queries, once parameterized, the validation can take as much as 25-30% of a P3 capacity frequently bringing service to a halt (100% utilisation)

This is preventing us from democratizing MS Paginated Reports (as they are a risk to our capacity)

Validation (which happens automatically whenever the query is changed) attempts to validate using what appears to be every possible value for the parameters (unless we manually set defaults, something that needs to be done in two separate places incidentally)

• Obviously the software should not bring down a very large capacity because a manual default has not been set, to validate a query that works in subseconds when parameters are passed

Report Builder validation and the DAX Query building experience needs a good revisit as it is fraught with bugs and large validation issues

1. Validation should only occur for one value per parameter (even if no defaults have been set)
2. Parameter defaults should be set in only one place (currently these need to be set in both the parameter and the query designer view)
3. Updates to the query should not mean that the parameters need to be removed (from the dataset and the query) and reinstated (as otherwise we get the parameter is not registered)