Getting Syntax error in Get rows SQL Connector

Like (0) Share

Report

Posted on 12 Jul 2023 15:03:30 by DBTS7

Hi,

I'm getting syntax error when executing a query in Get rows V2 filter query.

The query I'm executing is Select * from tablename where a<>0.00 or b<>0.00 or c<>0.00 ......(assume15 columns ).

The error I'm getting is: Syntax error at position 8 (whole select query) client id : .(some client id)

How I can solve this? as I want to update my sharepoint list from SQL Table using automate flow.

Thanks

All responses (5)

Answers (0)

DBTS7 on 18 Jul 2023 at 04:28:30

Like (0)

Report

Re: Getting Syntax error in Get rows SQL Connector

Hi,
Any solution for this?
or Is it the issue from microsoft itself?

Thanks
DBTS7 on 17 Jul 2023 at 10:25:22

Like (0)

Report

Re: Getting Syntax error in Get rows SQL Connector

Hi,
I'm using nvarchar(8) for the column type .
and Execute a SQL query action is running successfully. Not sure what I'm doing wrong...
Expiscornovus 31,652 Most Valuable Professional on 17 Jul 2023 at 08:32:24

Like (0)

Report

Re: Getting Syntax error in Get rows SQL Connector

Hi @DBTS7,

What type of column are you using in your query? Is it a string type of column or a integer/number?

Can you also try the Execute a SQL query action with your original SQL query to see if that makes a difference?
DBTS7 on 17 Jul 2023 at 07:07:27

Like (0)

Report

Re: Getting Syntax error in Get rows SQL Connector

Hi @Expiscornovus , Thanks for your reply,
But now the error occurred because of Pagination.
The below is the screenshot of trigger
and this is the pagination screenshot:
Whenever I'm enabling pagination, then I'm getting an error:

. Without enabling pagination, the flow is working fine (but only giving 2048 values by default)

What am i doing wrong here?
Expiscornovus 31,652 Most Valuable Professional on 13 Jul 2023 at 10:23:35

Like (0)

Report
Re: Getting Syntax error in Get rows SQL Connector

Hi @DBTS7,

The Filter Query field in the Get rows (v2) action expects an OData type of filter. I see you used the SQL query instead.

Try something like below. Replacing <> by not equal (ne).

(a ne 0.00) or (b ne 0.00) or (c ne 0.00)

Or you can also have a look at the Execute a SQL query (V2) action instead, that action should be able to handle a SQL query:

https://learn.microsoft.com/en-us/connectors/sql/#execute-a-sql-query-(v2)