cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Frequent Visitor

Bug - Saving New Forms with "Attachments" field, broken.

PowerApps SharePoint form won't let me save.

My PowerApps form for SharePoint List broke yesterday.  I ruled it down to the "Attachments" field.  We were only using this to display the attachments (not attach them).  Any "New" item created won't let us save the record when we have the "Attachments" field on our form.  The form works if I remove this field.  Not sure if this is related to any recent changes?  Anyone else experiencing this issue?  It was working before, but now we have to remove this field as a temporary workaround.  I've also created a simple list and new PowerApp and can replicate the issue on that too.

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

@jovan Thanks for the response. I should have acome back to the forum and updated it (my bad). The app is fine and upto the latest version, but this behavior was happening for a certain group of users, and we were able to identify the issue occurring due to a "restricted contribute" custom permission level. Reverting to OOTB "contribute" permission level fixed it. The only difference was the "restircted contribute" did not allow delete. Not sure why just removing the delete privileges would affect it, but might help someone else facing a similar problem.

View solution in original post

9 REPLIES 9
Highlighted
Frequent Visitor

Thank you, so much!!!! I had the same problem and couldn't figure it out.  I know it had to come about during the PowerApps updates yesterday or the day before, because I reverted back to earlier and as soon as I would make a change I wouldn't be able to save.  I've been going out of my mind for a day now with this.  Thanks again!

Highlighted

I found a workaround.  The PowerApp form doesn't like it when you add the "Attachments" DataCard pulled from the Data Source.  However, If you create a custom blank data card.  Then add the "Attachments" control from the drop down at the top, the form allows you to save again and still maintain this field.  You need to populate at least the item field for this control with the following:  ThisItem.'{Attachments}'

 Capture.JPG

Highlighted

You are correct, this is indeed a bug.  New items cannot be created if the Attachments control is present on the form.

 

The fix to this bug is ready and will be released by the end of February at the latest.  We are also looking into the possibility of releasing it sooner.

Highlighted
Frequent Visitor

What is the ETA on adding attachments to a new form that saves to the sharepoint list?

Highlighted

ETA for saving new attachments is early March.

- not filipk@microsoft.com, please private message me if you can't share with everyone
Highlighted
Anonymous
Not applicable

Hi all,

 

I realize that this has already been identified as a bug, and that the rough ETA on a fix is early March, but I was wondering if once fixed, will there be an announcement anywhere so we know that the fix has been implemented?

 

Thanks so much!

Highlighted
Frequent Visitor

We are still experiencing the issue of not saving attachments. Has the fix been pushed out yet? I am unable to find any further information in the message center as well.

Highlighted

@chetangarude , has your app been updated since the fix?

To make sure: you can just edit the app, make any change (even just a color of some label), and save it.  That should ensure that your app is on the newest version.

If the bug still repros then, can you please open a support call?

PS: to answer your question, the fix was published well over a year ago, so unless your app has not been updated in a very long time, this would have to be a completely different issue.  If this was somehow a regression, I would expect others to be running into it too.

Highlighted

@jovan Thanks for the response. I should have acome back to the forum and updated it (my bad). The app is fine and upto the latest version, but this behavior was happening for a certain group of users, and we were able to identify the issue occurring due to a "restricted contribute" custom permission level. Reverting to OOTB "contribute" permission level fixed it. The only difference was the "restircted contribute" did not allow delete. Not sure why just removing the delete privileges would affect it, but might help someone else facing a similar problem.

View solution in original post

Helpful resources

Announcements
Community Conference

Power Platform Community Conference

Check out the on demand sessions that are available now!

News & Announcements

Community Blog

Stay up tp date on the latest blogs and activities in the community News & Announcements.

secondImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

Community Highlights

Community Highlights

Check out the Power Platform Community Highlights

Top Solution Authors
Top Kudoed Authors
Users online (7,564)