Answered

Maximum character count increased on URL column, but still getting "too long" error

(0) Share

Report

Posted on by RobHardy

154

I have a dataverse table with a URL column, which was originally created with the Maximum character count set to the default of 100. After getting errors, I increased this to 500 characters, but I'm still getting the errors in the PowerAutomate flow which creates items:

The 'inputs.parameters' of workflow operation 'Add_a_new_row_-_movement' of type 'OpenApiConnection' is not valid. Error details: The API operation 'CreateRecord' requires the property 'item/abloads_outwardmap' to be a string of maximum length '100' but is of length '299'.

This is how the column is set up:

I've tried publishing all customisations in the solution containing both the flow and the table.

Any suggestions welcome. Thank you.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (1)

Michael E. Gernaey 53,960 Moderator on at

Like (0)

Report
Copy link

Link copied!

@RobHardy

Hi, I definitely understand the frustration, and I know you said you did, but to me this feels like
1) you updated the wrong field to 500 or at least this error is now a different field
2) somehow you didnt click save on the change and then when you published it didn't publish correctly
3) the flow is pointing to the wrong environment or wrong table.

You could always remove the connector and re-add it to see if that solves, it, but if not, then it has to be 1 2 or 3.

If I have helped you, I would really appreciate if you please Mark my answer as Resolved/Answered, and give it a thumbs up, so it can help others

Cheers

Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

Was this reply helpful? Yes No
Verified answer

RobHardy 154 on at

Like (0)

Report
Copy link

Link copied!

Thanks for the response, @FLMike, but if you look at the error message and the screenshot, you will see that the logical name of the column matches (so same column), the "Save" button is greyed out (indicating that it had been clicked), and definitely the correct table (which only exists at the moment in one environment).

In the end, I deleted the column, and re-created it with the same name, which resolved the issue.

Was this reply helpful? Yes No
ChrisPiasecki 6,422 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Hi @RobHardy,

In general I would avoid deleting and recreating columns with the same name, unless they have not yet been pushed to downstream environments like production. It can cause your solution imports to fail and require you to do an extra solution import without the column to delete the old one, then reimport with the new one, but that will result in data loss still. So exercise caution.

Assuming you already published customizations, the issue is likely stale metadata in the Flow. Usually the fix is to remove/readd the Dataverse actions that reference that column so that it retrieves up to date metadata.

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

1 people found this reply helpful.

Was this reply helpful? Yes No