Power Apps Canvas App Version 3.22022.23 BUG on SaveData() – There was a problem saving your data. Name could be too long.

[DKassian]

Following update to Power Apps version 3.22022.23 a bug has been identified that is impacting 100% of our production and development applications that use the SaveData() function, where as soon as the collection being saved has a certain number of records in it, there is an error “There was a problem saving your data. Name could be too long.” displayed to the user.

See screenshot from production application displaying this error:

To better test the issue, we created a simple canvas app that has the following functionality:

1. Number entry box to define number of records to collect,
2. Button to collect a single column collection, with n number of records from step 1
3. Button to run “SaveData” function on the collection created in Step 2

Using this test app, we were able to determine the number of records stored in a collection that will then start returning an error is between 1700 and 1720. This aligns to the issues we are seeing in our production apps. This is not a large number of records for an enterprise application, and to date we have never had these issues.

Our testing indicates so far that the data is indeed being saved, despite the error message. However, it is causing mayhem with users when they see error messages in the field. This is completely unacceptable to have this behavior change in an “enterprise grade” platform. We have had to roll back apps to prior versions to prevent this error message from displaying. At this point we are effectively unable to create or update any of our applications.

TEST APP, no error:

TEST APP: Errors

We have performed some additional test scenarios:

1. Collection is single column, and contains a single integer in each cell:

Record count where error is displayed: 1,700 to 1,750

1. Collection is multi column, and contains 150 words of random text in each cell (much larger collection):

Record count where error is displayed: 1,700 to 1,750

This testing leads us to believe it’s a count of records issue, not an issue with the size of the collection or the amount of data stored in the collection.

I hope someone is able to provide a solution to this bug, I have a ticket in with Microsoft, and will update this post with their response.

[daxjkent]

We have encountered this same issue and it as well is affecting our production applications with implications to our business operations. 

Sorry only a message of solidarity as we have not been able to resolve. 

Thanks for the additional information and troubleshooting to narrow down the issue.  Hopefully we have a resolution soon.

[PaulD1]

>>This is completely unacceptable to have this behavior change in an “enterprise grade” platform. 

I think this is a message we have to keep giving. QA/Testing is simply not good enough IMO - my clients have suffered too much disruption, and I have spent too many hours, trying to work-around bugs and issues which too often affect published Apps.

I no longer create new Power Apps, just try to maintain those already in production and encourage migrating to other platforms whenever that is under consideration.

[DKassian]

@PaulD1 We couldn't agree more, the lack of stability means a significant portion of our dev teams time is spent correcting bug and issues and working with users to get them through the issues. It's not a productive use of time, nor inspires confidence in the platform. We used to have a lot more stability on the model driven side, but over the past 6 months we've seen the same issues there, rapid rollouts, lack of testing, and bugs everywhere.

[DKassian]

We have gotten a response from Microsoft support that this issue is to be corrected on the March 7th release. I hope that is the case.

Additionally, as a workaround you can roll back the app to a prior version by editing the publisher. Going back 1 version solves this issue:

[Lukas1]

It's March 9th and in version 3.22021.27 the bug still appears. Thanks for the workaround!

[DKassian]

I've received an update from Microsoft that the fix has been delayed until the end of the month, I'm hoping it gets sorted by then for sure....

[Luis_V]

I've been following this Thread for a while too. We have the same problem with the error: "There was a problem saving your data. Name could be too long" on Saving Data greater than 1700 records. Does anyone have any info if this is going to be fixed in the next version of Power apps and when is it going to happen?

[JCD-JTP]

I have updated to the latest version 3.22031.24 released 5 days ago. The error persists..

[Lukas1]

Does anyone of you have an update on this?