Unanswered

ODBC and "invalid value" error when using % character within password - Power Automate desktop

(0) Share

Report

Posted on by unslog

hello.

Is there a workaround for Power Automate to accept % symbols within a SQL connection string using ODBC file DSN? It appears to deem the character as an "invalid value" despite wrapping the password in {} bracket.

See screenshot

Categories:

Using connectors

I have the same question (0)

All responses (4)

Answers (0)

lbendlin 8,474 Super User 2025 Season 2 on at

Like (1)

Report

Re: ODBC and "invalid value" error when using % character within password - Power Automate desktop

Single quotes around the password should work

c# - Escape ;(semicolon) in odbc connection string in app.config file - Stack Overflow

Was this reply helpful? Yes No
unslog 13 on at

Like (0)

Report

Re: ODBC and "invalid value" error when using % character within password - Power Automate desktop

Thanks for reply, however that doesn't work.

It appears to be specifically a problem with the % symbol. I also tried other methods mentioned in the link you provided to no avail. the semi-colon within the password works with no problem. Doesn't even in to be wrapped with {} or ''

Was this reply helpful? Yes No
lbendlin 8,474 Super User 2025 Season 2 on at

Like (1)

Report

Re: ODBC and "invalid value" error when using % character within password - Power Automate desktop

How about %% ? Have you considered changing the password?

Was this reply helpful? Yes No
unslog 13 on at

Like (0)

Report

Re: ODBC and "invalid value" error when using % character within password - Power Automate desktop

Hi,

The %% kinda worked - i.e. the "invalid value" stopped appearing...however this then broke the next step "Execute SQL Query" as the SQL connection variable uses % symbols, so suspect a clash.

So the workaround to this (if anyone else experiences this behaviour) is to amalgamate the connection string with the SQL query (see screenshot), The only issue with is approach is I'm unable to close the SQL connection (which appears to depends on a connection string variable.

Was this reply helpful? Yes No