You are modifying a SQL Server Reporting Services (SSRS) report for a SQL Server Analysis Services (SSAS) cube. The report defines a report parameter of data type Date/Time with which users can…

By editing the dataset query parameter and changing its Value property to an expression - such as wrapping the Date/Time parameter in a Format() call to produce an MDX-compatible member key string like '[Date].[Date].&[yyyyMMdd]' - you resolve the type mismatch without rewriting the MDX query or adding subqueries. This is the minimum-effort approach because only the parameter value mapping changes, leaving the existing MDX query structure intact.

Changing the Name property of the dataset query parameter only affects how the parameter is referenced internally and does not resolve the underlying type incompatibility between a .NET DateTime value and the string-based MDX member format the SSAS cube requires.

Using a StrToSet subcube subquery would resolve the type issue but requires substantially rewriting the MDX query structure, making it a higher-effort solution than simply modifying the parameter value expression.

Rewriting the dataset query in T-SQL replaces the MDX cube query entirely with a relational query, which is the highest-effort option and changes the fundamental data retrieval architecture away from SSAS.