Dataverse column updated max length not pushing through to data

[Anonymous]

Hi All, 

I created a column with a character max length of 100. It then became evident this wasn't enough so I upped it to 500.

This information seemed to come through fine within PowerApps however the information when submitted to the dataverse table is still limited to the 100 characters and thus still having the same issues.

Does anyone know how I could resolve this issue?

Thanks!

[rampprakash]

Hello @Anonymous,

Importing thing after changing the column we need to PUBISH Entity and PUBLISH All Customization to get it fixed Successfully.

Suggestion : Try using Multiple Lines of text if we are going  more than 250.

Please mark as Answer if it is helpful and provide Kudos

Subscribe : https://www.youtube.com/channel/UCnGNN3hdlKBOr6PXotskNLA
Blog : https://microsoftcrmtechie.blogspot.com

[v-bofeng-msft]

Hi @Anonymous :

If you have already save the change(set the max length to 500) as @rampprakash said,and your app still not work.Please consider refresh your data source(Usually reopening the app will have the same effect):

I think this link may help you a lot:

https://powerusers.microsoft.com/t5/Power-Apps-Ideas/CDM-Maximum-lenght-on-data-type-quot-Text-quot-and-quot/idc-p/100748/highlight/true#M4359

Best Regards,

Bof

[Anonymous]

Neither have fixed the issue. Any other ideas?

[rampprakash]

Hello @Anonymous,

Delete the field in Dataverse if it does not contain a huge data then refresh the DataSource in PowerApps then create the same field again in PowerApps then publish the solution, then refresh the DataSource in PowerApps again and try again.

Try with both Single and Multi line field.

Please mark as Answer if it is helpful and provide Kudos

Subscribe : https://www.youtube.com/channel/UCnGNN3hdlKBOr6PXotskNLA
Blog : https://microsoftcrmtechie.blogspot.com

[Anonymous]

The app is currently live and being utilised. 

Although this might be something I could do out of hours its something I have been trying to avoid. 

Thank you though, I will let you know how I go. 

[rampprakash]

Hi @Anonymous,

One more suggestion, try creating another field in the DataVerse environment before deleting and and try using the same from PowerApps if it works fine.

Write a one time flow to copy the data from One field to another field to avoid data loss,

or export the data from excel and import by mapping the data from one field to another.

if all goes good just hide that field from the form then enable the new field.

let me know if you need more clarity

Please mark as Answer if it is helpful and provide Kudos

Subscribe : https://www.youtube.com/channel/UCnGNN3hdlKBOr6PXotskNLA
Blog : https://microsoftcrmtechie.blogspot.com

[coatsyMSFT]

I know this is from a long time ago, but I just encountered the same issue (from Power Automate).

The fix for me was to remove the UpdateRow action and replace it with an identical one.

[chuck3138]

I just tried changing the MaxCharacter length from 100 to 300 and it does work for me. 

Make sure you are editing column properties directly in the Dataverse Table itself, not in the Canvas Apps designer.

Also, check if your security role allow you to make changes on the Dataverse Table.

Share a canvas app with your organization - Power Apps | Microsoft Learn

[MartinNadeau]

Juste got the same issue.
One field in an entity was 100 characters then we increased it to 160.
then when running the UpdateRow action, it still said that the field I wanted to update was too long (112 over 100). 
We tried many things without positive results. 

We were about to remove the UpdateRow action (to rebuild it) as suggested by coatsyMSFT

But we also found out that switching the connection reference on that box (still poiniting to the same dataverse) resolved the issue. As if it would "scan/read" the fields metadata.
Then I also replaced the connection reference back to what it was and it works as well.