Flow error to many characters in dataverse table?

(0) Share

Report

Posted on by Oskarkuus

1,097

I have a flow that updates a dataverse table.

I get this error :
"
The 'inputs.parameters' of workflow operation 'Update_a_row' of type 'OpenApiConnection' is not valid. Error details: The API operation 'UpdateRecord' requires the property 'item/crf35_saljuppsag_tjanstavtal' to be a string of maximum length '100' but is of length '107'.
"
It is clear that the amount of characthers is to many for that column in the table.

But if i go to the dataverse table and look at the column "crf35_saljuppsag_tjanstavtal"

in the column settings i see this:

I have tried to update the value. Save and update the flow. But nothing works. It refuse to accept that it should save more than 100.

What can i do?

Categories:

General topics

I have the same question (2)

All responses (4)

Answers (1)

Verified answer

Oskarkuus 1,097 on at

Like (3)

Report
Copy link

Link copied!

Ofcourse i solved it directly after posting.

To fix the issue i needed to remove the dataverse (update row) connector in Power Automate.

And then save the flow

Then create a new connector and set that up as the old one.

Then i got the settings and the flow could run with no errors.

Was this reply helpful? Yes No
GeorgeRobinson 8 on at

Like (1)

Report
Copy link

Link copied!

A problem with the above approach is if you had done a lot of work in matching say JSON fields to the table fields for the update. I found that if you copy the connector to the clipboard, delete the connector, then paste it back and save then you get the same outcome that Oskarkuus describes but without losing your work.

But seriously though - why on earth has Microsoft not given us a "refresh connection" type option for these connectors?!

Was this reply helpful? Yes No
GeorgeRobinson 8 on at

Like (1)

Report
Copy link

Link copied!

I thought this worked but sadly it didn't. So Oskarkuus' solution is what I've gone for and had to tie every single field again. What a waste of two hours! I would say the strap line for PowerApps should be "Low code, high effort" when it comes to this sort of thing.

Was this reply helpful? Yes No
mhoelling 57 on at

Like (2)

Report
Copy link

Link copied!

This is a bit old, but I just encountered a similar problem, so for the record and if someone else falls across this...

I got the message that the character count exceeded the number of characters, I changed that in the corresponding column of my dataverse table, and the error kept appearing, no matter what I did in terms of refreshing, publishing the table etc.

What finally did the trick was to "turn off" the flow and then turn it on again.

Somehow this seems to trigger a refresh of the metadata for the flow.

Maybe there is a better solution, but this is what worked for me and is relatively "painless" to do.

Was this reply helpful? Yes No