Why won't Power Apps let me save my form?

[wwisegl]

I am following along in the How to build a model-driven app module and am having an issue saving both new forms and edits to existing forms. When I follow the directions in either scenario, the designer displays this message:

Error: We ran into a problem saving the form. Please try again. (SessionID: 526b2500-a56b-11ec-9fa5-bd19916277d4)

Can anyone help me get past this issue? All I've done up to this point is follow the steps outlined in the module. Do I need additional permissions to be able to do this?

[timl]

Hi @wwisegl 

If you've not done so, I'd recommend that you subscribe to the developer plan and that you carry out the tutorial in your developer environment.

https://docs.microsoft.com/en-us/powerapps/maker/developer-plan

The account entity is a core entity and it's possible that your system administrator has applied additional permissions. The cause of the error might also be related to licensing.

If all you want to do at this point is to follow the training, using a developer environment would be the easiest option.

[wwisegl]

Thanks! I really appreciate this advice. I'll check it out.

[ADPerkin]

So this probably wont help this user but may help someone else with same issue.

I hit the same message: 

@ Error: We ran into a problem saving the form. Please try again. (SessionlD: 00ccb6e0-261c-1 lee-bed9-f91917589151)

Saving, Publishing, Save As didn't work. It was also my default Form so creating new picked this up and whilst form got created wouldn't save, nor could I change form order.

Then just before I attempted to delete it, I tried turning the form off and got a different error:

@ Turn off failed. The dependent component EntityRelationship (Id—hadf contact hadf groupmember 878) does not exist. Failure trying to associate it with SystemForm (Id=70960b27-f4e3-ed11-8846-6045bdf1e702) as a dependency. Missing dependency lookup type = PrimaryNameLookup.

So this was a custom relationship (not one I recognised - possibly auto generated based on the appended sequence number)- but more so it was a clue. Luckily I spotted that the Table field of the subgrid in a section was mysteriously now empty?  So I re-populated it, finally saved the form and everything worked.

Its a huge shame that the second error message wasn't displayed straight away instead of the fairly rubbish generic one. So rule is try turning form off you may get a new clue...
 

Hope this helps someone at some point - a few hours of my life were wasted working this out...