topic Re: Query Parameters for Teradata SQL Query in Report Builder in Report Server

Query Parameters for Teradata SQL Query in Report Builder

Smcqueen2024 — Thu, 20 Jun 2024 02:30:44 GMT

I am trying to use query parameters in a query to Teradata. When I use the (@ParameterName) syntax, I get a Teradata error saying the number of parameters called does not match the number of parameters defined. My assumption is that the call for parameters in Teradata is the same as Report Builder, so Teradata is getting confused? I also tried the M Query parameter call "&ParameterName" and it actually called the value. But I got an error saying Teradata expected something between a unicode value and the parameter. Is there a way to escape the parameter call? Or there some other syntax I can use?

Re: Query Parameters for Teradata SQL Query in Report Builder

Anonymous — Fri, 21 Jun 2024 02:50:47 GMT

Hi Smcqueen2024 ,

Please check the following unicode values and parameters. Is there a detailed screenshot of the error?

Best Regards,

Xianda Tang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Re: Query Parameters for Teradata SQL Query in Report Builder

rnola16 — Tue, 04 Feb 2025 19:58:43 GMT

Were you able to get past this error ? I use the same Teradata + Report Builder. What is the correct syntax in defining a parameter in the SQL ?

Thanks.

Re: Query Parameters for Teradata SQL Query in Report Builder

Poojara_D12 — Fri, 14 Feb 2025 12:55:27 GMT

Hi Smcqueen2024

When using query parameters in Teradata within Power BI Report Builder, the standard @ParameterName syntax does not work because Teradata does not support named parameters like SQL Server. Instead, Teradata uses question marks (?) as placeholders for query parameters. However, Power BI Report Builder does not directly bind parameters to ?, so an explicit CAST statement is required. To ensure proper execution, modify the query by replacing @ParameterName with ? and explicitly casting it, such as CAST(? AS VARCHAR(100)). In Report Builder, navigate to the dataset properties and correctly map the ? placeholder to the corresponding parameter. If you encounter errors when using &ParameterName (which is specific to Power Query), avoid that approach. Alternatively, you can handle dynamic filtering by modifying the query to allow for an "All Values" option, using a condition like WHERE ColumnName = ? OR ? IS NULL. By following this approach, Teradata will correctly interpret the parameters, preventing syntax errors and ensuring proper filtering in the report.