SaveData() Error / possible Bug. "File name might be too long"

[Chalico]

I get the message mentioned in the title (There was a problem saving your data, name file might be too long), all of a sudden, when saving data on my app. I've been using the SaveData/ LoadData for months before now without any problems until last Friday. Shortened all names (collections and reference names) to double-check even though it shouldnt be a concern because as I said, it was working for several weeks before. still no luck. As mentioned in this thread - https://powerusers.microsoft.com/t5/Building-Power-Apps/There-was-a-problem-saving-your-data-Name-co... - , might be an issue with the new PowerApps version. Any ideas? If not, how to change the PowerApp version? (roll back to a previous one). Thanks

[EddieE]

@Chalico 

If you have definitely ruled out that it cannot be the file name length then some options you can try are:

1. Create a MS Support ticket, here:

https://admin.powerplatform.microsoft.com/support

If you go to Known issues with PowerApps and Active there is a issue relating to Offline Apps, which may / may not be related to your issue, ie

2. Update the Authoring Version inside your app, then Save & Publish

 - Inside your app Editor, Go to Settings --> Support --> Authoring Version --> Edit --> Select the version you want to use then Reload & Apply, ie

3. Rollback to a working version of the app

 - from your app list in make.powerapps.com --> select the 3 dots beside your app --> select Details --> select Versions --> select the version you know works --> select 3 dots and click Restore, ie

 - In my example above, Version 131 will become Version 138, but it won't yet be LIVE.

 - Click the 3 dots beside your Restored Version (eg Version 138) and click 'Publish this version'

You can always roll back to any listed older versions if you make a mistake.

[jhsu]

I ran into this issue today too. It appears to be an issue with authoring version 3.24023.14. What's even stranger is that even after reverting the authoring version to the previous 3.24022.17, the app continues to publish in version 3.24023.14. The only way we have been able to get to the previous authoring version is to rollback to a previous version (Option 3 that EddieE mentioned). However, that proves to be problematic as we can't publish any new changes as editing will update the authoring version right back to 3.24023.14. 

Looking at the release notes for version 24023, Microsoft was making changes to offline functionality which may have inadvertently affected SaveData. 

[jhsu]

New update from my testing. I thought previously you could just change the authoring version and then publish to switch to the latest authoring version. It appears you need to change the authoring version, let the editor reload, make some sort of edit so you can save, and then publish. 

I have had success with reverting to 3.24022.17 and no longer get the error and SaveData does work.

[catra_does_pw]

Yes, happened to me. I get the same error. I tried to switch back to an older version, but since the app is being used in a scanner, it does not 'change' to older versions. 
And I just made a single modification to my app, I've added a pop up! 
I hope they can solve this problem as quickly as possible

[wolfcat]

This happened to us as well.  It started yesterday once we've uploaded / pushed / published a new version of our app.  I wish they would advise that a new authoring version was also going to be impacted, when publishing...

Chalk this up to another Microsoft update rollout failure!  

Thank you @Chalico  for finding this solution.  It works for us!!!! 

[EddieE]

@wolfcat @catra_does_pw @Chalico 

I'd suggest that you all create MS Support tickets on this issue, I find this is the quickest way for MS to action these things.

We had an issue with an app 2 weeks ago and after extension internal testing I decided it was a release issue and created a ticket with MS. Within 24-48hrs they had found there to a problem with the current release and implemented a global update. Sounds like this is something needed here as well.

[Chalico]

Thank you for your replies!

You have confirmed that this is an issue with the latest Power Apps version, and that going back to a previous one like the one ending with ".12" and publishing fixes this issue.

Please give this topic some love by liking it, so more people can see this, since it seems this is the only topic that addresses this issue. thanks again!

[wolfcat]

Microsoft released a new version this morning, and now the app is doing the same thing.  Is there a way to avoid having them change the authoring version, whenever we release an update?  Otherwise, whenever we now make an update to the app, we have to tell them to uninstall and reinstall the application.  

@Chalico Great catch!  Thank you for that find.  Saved us a lot of time troubleshooting!