Parse error at provide a DATE format input parameter/variable

[mitrechosa]

Hi all,

When try to anwser an Input parameter with date format it should be whitout single quotes, and as far I know and I tested it is not possible with the current version.

how to reproduce:

*Create an mandatory Input parameter with date format for example DATE1 in the view.
*Map the parameter in the model to a date variable
*try to generate ODATA request by using the connector by passing the following input parameters.
DATE1='2024-01-01'
DATE1=2024-01-01

none of them worked

Example ODATA REQUEST by DSP

https://SERVER/api/v1/dwc/consumption/relational/TEST/VW_TEST/VW_TEST(DATE1=2024-01-01)/Set

there is a workaround by converting the IP in the view to the string format but it is necessary to handle dates

regards.

[gustavokath]

Hi @mitrechosa,

Could you confirm if the issue is related to the PowerBI connector itself or to the Consumption APIs in general?

I've found an issue around the date/datatime being between single quotes some weeks ago which should be already resolved, could also check if the issue still exist?

Best Regards
Gustavo Kath

[mitrechosa]

Hi Gustavokath, I guess is problem with the connector itself.

this is my analytic model and variable.

and this is the same request in powerbi. tested with single quotes as well.

PBI response.

Detalles: "Microsoft.Mashup.Engine1.Library.Resources.HttpResource: Error en la solicitud:
Versión de OData: 3 y 4, error: Error en el servidor remoto: (400) Solicitud incorrecta. (Bad Request Error: Unable to process asset parameters: AUDAT is not a defined parameter. Please, check parameters definition.)
Versión de OData: 4, error: Error en el servidor remoto: (400) Solicitud incorrecta. (Bad Request Error: Unable to process asset parameters: AUDAT is not a defined parameter. Please, check parameters definition.)
Versión de OData: 3, error: Error en el servidor remoto: (400) Solicitud incorrecta. (Bad Request Error: Unable to process asset parameters: AUDAT is not a defined parameter. Please, check parameters definition.)"

but if you use another model with varchar variables, it works