You are viewing limited content. For full access, please sign in.

Question

Question

Cloud Query Rules - Input string was not in a correct format

Rules
Updated August 15
asked on August 14

You can get this error when calling a query that inserts data into a lookup table.

How can a input, of type string, have formatting requirements? As far as I know a string means any characters in any order.

I don't know what to fix about my 2 string inputs, they look like strings to me

0 0

Replies

replied on August 14

Was it around 11:06 Pacific, insert query from your SP account? Our logs caught it as 

" CAN'T CAST VALUE TO TYPE SYSTEM.DECIMAL. THE INPUT STRING '' WAS NOT IN A CORRECT FORMAT.", so it's about one of the number columns in your table.

0 0
replied on August 14

That time sounds right. It is telling me that there is a problem with a string input, but if it is actually a number input that leaves just one of my inputs since all the rest are of different types.

The input it is failing on is 2100 in a test I just ran.

Looks like a good number to me, it succeeded with the number 3080 just before

Can we just get the name of the input and the value that is invalid rather than the type of the input? Makes it easier to troubleshoot.

The way I get the value is to add a track tokens just before the rule then pull up the instance history, filter by the token I am using, and scroll all the way down to the last value listed (because it is running in a for each value loop). I have no functions or modifications set on the token that is being used as in input for the rule.

0 0
replied on August 15 • Show version history

I already filed a request to make the messages clearer (reference ID # 60854). It might not be possible to get as detailed as specific parameter, but we should be able to tell you what the expected type was to narrow down troubleshooting.

The error matches SQL's error style, it's basically saying "this value does not look like what i was expecting, so I'm thinking it's the most permissive format i can think of, which is string". So it's somewhat misleading because it implies that it's about string columns. 

Where do you get the values from? Is it possible that there's a leading or trailing space or other non-printable character in it?

0 0
replied on August 15

It is retrieved from a template field of type number so it should be clean of any space characters. No modifications that I can find being done on the value that would add any characters to it, it just comes from a template and goes into the table. The one conditional decision path that could possibly try to modify it with a calculation is never executed because it's conditions are never reached.

The workflow pulls a number from the template and inserts it into a lookup table.

It fails on a different number each time. It always fails on the 36th attempt but my track tokens only shows 13 values yet I have a create token activity for each iteration. So I might be misunderstanding what track tokens actually does? I expect to see 36 track token objects, not just 1 with 13 values listed.

The workflow retrieves the values then puts them into an Assign Token Value activity since the For Each Value only accepts 1 field, not all of them.

Then I use the Assign Token Value tokens as input for the rule. I collapsed the conditional decision area because they are not modifying the token I am using for the number argument, only the tokens used for the integer arguments.

Maybe there is a another way I should be looking for the value that it is unhappy about, I want to make sure I am not looking at the wrong value when troubleshooting.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...