cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
GrischkePro
Advocate III
Advocate III

SubmitForm function can only work on a form. Wrong kind of control input is given...

All of a sudden, the Submit button stops working, producing this error:

 

paerror.png

 

It was working fine and I changed NOTHING in my EditForm.

 

This is a custom button. The original tick in the upper right corner with exactly the same formula/settings works just fine.

 

Any idea?

55 REPLIES 55

Yes via the admin portal


@rachelkettle wrote:

Yes via the admin portal


Ok, I did the same.


@Anonymous wrote:

Hello,

 

Agreed. There seems to many posts about SUBMITFORM having issues. I did all variants of rebuilding. Recreated the sql connector. Re-imported from the TEST environment and so on. Actually, this app works fine in the TEST and DEV environments. I did figure out a work around though. I changed the SUBMITFORM to PATCH. 

 

I did a test with Patch and it works, but I'm not sure if I want to go down this route without breaking something else 🤬🤬🤬 I don't have time for this and testing 🤬🤬🤬

 

Patch(
    List1,
    Defaults(List1),
    {Title: DataCardValue4.Text}
);
Navigate(
    BrowseScreen1,
    ScreenTransition.Fade
)

I'll wait to see what M$ are going to do about this @$%^🤬🤬🤬🤬🤬🤬🤬

Ah thanks, although i also don't fancy going down the route of changing the submit forms to patches either...i have found that if the button sits within the form itself it produces the error and doesn't perform an update, but if the button sits outside the form - with the exact same submitform(formname) command it works...!

 

I can use this as a workaround for developing but will need the buttons to sit within the forms when deploying Live so i hope this is fixed asap!! 


@rachelkettle wrote:

Ah thanks, although i also don't fancy going down the route of changing the submit forms to patches either...i have found that if the button sits within the form itself it produces the error and doesn't perform an update, but if the button sits outside the form - with the exact same submitform(formname) command it works...!

 

I can use this as a workaround for developing but will need the buttons to sit within the forms when deploying Live so i hope this is fixed asap!! 


Hence why the original Tick button in the original QuickActionBar worked for me - this area is outside of the form. The 🤬

 

Next thing they'll break is the Patch function 🥶🥶🥶

I just ran into this issue as well.  Same error message and everything.  It happened randomly after saving my app.

Same here! Please let me know if you have any news regarding this!

Reverting to the previous version ending in .14 solved it for me. 

That fix may work for editing it, but every time you publish the app, it updates to the newest version.

Also... that doesn't work for me even in the development studio.  I'm not sure what the difference is for you and me.

Yes agreed. 

 

Also I found it only fixed the problems for PowerApps apps - it does not solve the problem for PowerApps forms which also display the error even when being in version ending .14!

Helpful resources

Announcements
PA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

MBAS Attendee Badge

Claim Your Badge & Digital Swag!

Check out how to claim yours today!

secondImage

Are Your Ready?

Test your skills now with the Cloud Skill Challenge.

secondImage

Demo Extravaganza is Back!

We are excited to announce that Demo Extravaganza for 2021 has started!

MBAS on Demand

Microsoft Business Applications Summit sessions

On-demand access to all the great content presented by the product teams and community members! #MSBizAppsSummit #CommunityRocks

Top Solution Authors
Top Kudoed Authors
Users online (69,007)