Hi, Using the action "Get Rows" from SQL Server standard connector: With only the aggregation transformation it works fine With only the filter query it works fine With both it fails (see picture, it generates a BadRequest) Thanks for your help.

Ok found it: since the aggregate rename the column, I had to replace the name of the previous column "pixocect" with the new ones "DistinctInvoices". With this change, it works.

[SQL Server] Odata issue with aggregation and filter

Sylvain 216

Hi,
Using the action "Get Rows" from SQL Server standard connector:

With only the aggregation transformation it works fine
With only the filter query it works fine
With both it fails (see picture, it generates a BadRequest)

Thanks for your help.

Accepted answer

Sylvain 216 Reputation points

2021-09-15T08:23:42.61+00:00

Ok found it: since the aggregate rename the column, I had to replace the name of the previous column "pixocect" with the new ones "DistinctInvoices".
With this change, it works.
Please sign in to rate this answer.

1 person found this answer helpful.
MayankBargali-MSFT 70,801 Reputation points

2021-09-15T08:43:24.66+00:00

@Sylvain Thanks for your answer and glad to know that you were able to resolve the issue. Feel free to 'Accept as Answer' so it can help other community members facing the similar issue.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

[SQL Server] Odata issue with aggregation and filter

0 additional answers

Your answer