cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

SubmitForm function not working

I am kind of new to Power Apps, but have a basic understanding of how things work.  I have a canvas app that was generated from a SharePoint list.  I modified the canvas app to meet business requirements, such as adding data validation.  Also, a new label needed to be created in the form that calculates its text property based on other conditions in the form, or more specifically concatenates two values of text from the form together.  The text property of the label needs to be fed back into the SharePoint list.  I created the new column in the SharePoint list, and then added the related data card in the canvas app so that the data fields could be mapped appropriately.

 

When I fill in all of the fields on the form and select the submit (check) icon button in the top right of the screen, nothing happens.  Power Apps has a couple dots scroll across the screen, but the two things that I would expect to occur are not occurring (the form would clear, and new record would be in SharePoint list).  There are no errors shown during submission of the form, nor are there any errors in the canvas app designer, aside from accessibility warnings, which is not a business requirement to address yet.

 

For your reference, I have not modified the behavior of the SubmitForm () function, which is shown as below:

 

SubmitForm(AddUnifiedGroup_EditForm)

 

I've seen some related posts on this topic with some suggesting that a field may be required to be mandatory in the SharePoint list and not required in the canvas app, but that is a moot point since I've filled out all fields of the form.  What would REALLY be helpful is seeing SOME sort of error to help me diagnose the problem.  Since I have no error, I need someone's help on these forums.

1 ACCEPTED SOLUTION

Accepted Solutions

I fixed the problem.  turns out that I had renamed some columns in the SharePoint list because some had spaces in the name, which resulted in the column name field being shown as Group_x0020_Type.  So I thought if I removed the space from the column name, that would remove the _0020_ from the field, and so therefore I had updated the app to remove that part of the data field name.  Only after more closely looking at the Monitoring of the app did I realize that the SharePoint field name will never change, no matter how much you try to rename it, since renaming it is simply changing the display name of the field, and not the actual field name.

To easily revert my bad changes, I created a new canvas app from the SharePoint list, and copied over the values to the appropriate sections that I had modified in my original app.  Problem solved.

View solution in original post

13 REPLIES 13

@tgarrity 

Another reason for failure to submit the data in the form is if you modify the source in your galley where you choose the record to edit, you must have a specific way for your form to recognize the record. Make the Item property of the form something like: Lookup(datasource, ID= Gallery1.Selected.ID).

Does the form work to submit new data? Is the DataSource property of the form the actual list in SharePoint? You can put a function like Notify()  in the OnSuccess and OnFailure properties of the form to troubleshoot; in OnSuccess: Notify( "It Worked!", NotificationType.Success); ResetForm(AddUnifiedGroup_EditForm)
OnFailure:  Notify("Darn it failed",NotificationType.Error)

Unfortunately I did not understand the first paragraph.  The (3rd) screen that I have the form on does not contain a gallery.  I am not trying to modify any existing records in the gallery (SharePoint list).  It's just a form.  And I'm creating a new record when submitting the form.  If I make a brand new canvas app from the same SharePoint list, without modifying the form, I am able to create a new record.  The form submits as expected, and I see the new record show up in the SharePoint list.

The DataSource property is still the same as it was originally [@'Unified Group Provisioning'], which is the name of the SharePoint list.

I implemented the OnSuccess and OnFailure functions that you mentioned, which confirmed to me that the form failed to submit, but unfortunately I am no closer to actually diagnosing what is happening.

I just found this "Monitor" feature and started the app and attempted to submit it.  I noticed I got a few of the errors with the custom connector that I created for querying Azure AD using the Microsoft Graph, which as you can tell I called MSGraph, and an operation called GetGroups, which gets all Azure AD group names.  I assign the result of the GetGroups operation to a variable called AADGroups, and is triggered when a user clicks a button on the form called Preview_Button.

I first get this, which has a Success result (status: 200), and I replaced the data in the returned data with { --- }.

{
  "status": 200,
  "duration": 218.94,
  "dataSource": "MSGraph",
  "responseSize": 7212,
  "controlName": "Preview_Button",
  "propertyName": "OnSelect",
  "nodeId": 55,
  "formulaData": {
    "script": "",
    "spanStart": null,
    "spanEnd": null
  },
  "data": { --- }
}

But immediately after that, I get 7 errors (status: null) stating the below

{
  "status": null,
  "duration": null,
  "dataSource": null,
  "responseSize": null,
  "controlName": null,
  "propertyName": null,
  "nodeId": null,
  "formulaData": {
    "script": "",
    "spanStart": null,
    "spanEnd": null
  },
  "data": {
    "property": "onPremisesSyncEnabled",
    "info": "JSON parsing error, expected 'string' but got 'boolean'.",
    "issue": "This is more likely due to mismatch between metadata and actual data received. Please ensure your metadata and server response match."
  }
}

 Could this be the reason why I am not able to submit the form?  If so, I'm still not sure what it is I need to do to proceed in fixing this.

ok I may be getting somewhere.  I went into the custom connector because I realized that the schema must have been misinterpreted when I provided what a response would look like.  I turned on the swagger to look at the definition for onPremisesSyncEnabled property.

I'm getting this error when I test the operation

Structural error at paths./v1.0/groups.get.responses.default.schema.properties.value.items.properties.onPremisesSyncEnabled.format
should be string
Jump to line 50

And here's line 49-50

 

onPremisesSyncEnabled: {type: boolean, description: onPremisesSyncEnabled, title: '', format: null}

 

The error goes away if I take off

 

, format: null

 

But then I get this error when I perform a test operation

Property ".value.Item.onPremisesSyncEnabled" type mismatch, Expected: "boolean", Actual: "string".

All I am trying to run is this HTTP request with this operation.

https://graph.microsoft.com/v1.0/groups

I don't even care about the value for the property onPremisesSyncEnabled.  I am only caring about the displayName property.

One other tidbit: the onPremisesSyncEnabled property can either be true or null.  It is never false.  Don't ask me why, I'm not the one who developed this attribute in the Microsoft Graph.

Turns out that the MSGraph custom connector is not at fault for the form submission failure.  Back to square one.

I fixed the problem.  turns out that I had renamed some columns in the SharePoint list because some had spaces in the name, which resulted in the column name field being shown as Group_x0020_Type.  So I thought if I removed the space from the column name, that would remove the _0020_ from the field, and so therefore I had updated the app to remove that part of the data field name.  Only after more closely looking at the Monitoring of the app did I realize that the SharePoint field name will never change, no matter how much you try to rename it, since renaming it is simply changing the display name of the field, and not the actual field name.

To easily revert my bad changes, I created a new canvas app from the SharePoint list, and copied over the values to the appropriate sections that I had modified in my original app.  Problem solved.

Hey @Drrickryp in 

Lookup(datasource, ID= Gallery1.Selected.ID).

What is ID? I see it on multiple posts but when I use it it's not a name that is recognized. 

In the Item property (the field called "Item". If I have a Datasource called 'Candidates' that I want to save this to...

I would write: 

Lookup(Candidates, ID= Gallery1.Selected.ID).

Is ID the column within the datasource? But won't the whole form just be pointed to a specific column? 

 

My gallery is using a datasource of a related datasource... it's items have for example ThisItem.ColumnName.Name to fetch the related records. 

@shavora 

What is your datasource? SharePoint, dataverse, Sql, etc?

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (712)