cancel
Showing results for 
Search instead for 
Did you mean: 

PowerApps Attachments to SharePoint lists size limit

Currently there is a limitation of uploading a file attachment size to max of 10 MB. SInce SPO can accept upto 250 MB per file in a list item, it makes sense to increase the attachment size in PowerApps to 250MB.

Status: Planned
Comments
Level: Power Up

@FilipK  Which is it? You're not expecting to "determine a timeline" in the next couple of months or you're not expected to implement a solution in the next couple of months? (MaxAttachmentSize = 10250MB)

 

I have a product developed for a customer that can't be implemented because of this 10MB bottleneck to a 250MB back-end. Is "a couple of months" 2 months or some indetermined period of time longer than that?

All we want is some clarity here.

PowerApps Staff

@Gimbal We are working to identify the the work needed (and hopefully get some of that completed) in the next 2 months.  It is too optimistic to think that the feature will be available for use in 2 months.

 

Also based on our current investigation, we'll be looking to increase the limit to 100 MB.  Going past that is likely not in the immediate roadmap.

Level: Powered On

100 MB works for my needs.  However, not sure why it is taking so long for such a basic feature that has already been implemented.  Just remove the 10 meg limit currently imposed.  The developer can decide if the performance hit is worth it.

 

I want to reiterate from a previous post, PowerApps is unusable for a wide variety of corporate apps including anything to do with SharePoint without the ability to attach reasonable sized documents.  In fact, I'm hard pressed to come up with a use case without this feature.  Photo sharing is not really a serious need.

Level: Powered On

I have to echo the concerns and aggravations of others. To wait a couple months (after waiting many months) only to be told it'll be a couple months more before it's even on the timeline is really disappointing. I don't understand how such an essential feature isn't a priority. Throttle upload speeds or add file compression options, do whatever you guys have to do, but this is seriously slowing down PowerApps adoption.

Level: Powered On

I also don't understand the delay on this feature. I have seen posts going back over a year. Our company has begun implementing PowerApps and have hit a roadblock with the 10MB limit. Even an increase up to 50MB would help, but 100MB and up is becoming more common. It's not fun to just tell the executives that we should be able to do this once Microsoft figures out how to solve their problem they have been working on for over a year and still can't tell us when it will be looked at seriously.

Level: Powered On

The delay of having this resolved is simple. The PowerApps architecture is an entire kludge and Microsoft really doesn't care about any of our concerns.


@kollikr wrote:

Currently there is a limitation of uploading a file attachment size to max of 10 MB. SInce SPO can accept upto 250 MB per file in a list item, it makes sense to increase the attachment size in PowerApps to 250MB.


 

PowerApps Staff
@DevelopAlways wrote:

The delay of having this resolved is simple. The PowerApps architecture is an entire kludge and Microsoft really doesn't care about any of our concerns.


@DevelopAlways shouldn't that be an "or" not an "and"?  Smiley Sad

Joking aside, I think that's fair criticism.  The answer is that it's definitely the former, not the latter.  And it's not really that architecture is a kludge, but we are trying to re-architect how PowerApps handles files, so they are never brought into app's memory if not needed in order to improve performance and make PowerApps viable on most mobile phones used accross the world.  To achieve this we are trying to make sure all attachments are loaded onto the device's storage and even written to the back-end from there, and there are many scenarios to consider for security, perfromance, use in apps, etc.  So while this is taking a lot longer than any of us would like, we are deeply comitted to getting this done.

As far as dates, I still haven't provided one because I don't have high confidence in a date yet.  I can say that it will be this year, hopfully by October, but this is not something you should base a whole project on yet.

I realize this is not much of a consolation to most on this thread, but we definitely care and take the just criticism seriously.

Level: Powered On

Filip, I really appreciate your answer.  I would suggest lifting the limit now and letting developers decide if it is a problem.  I for one do not need mobil and even a 10 minute load time is not an issue.  However, I can't develop anything in PowerApps without this feature as file attachments are always required in internal corp apps. 

PowerApps Staff

@gdavis53  Fair point.  We are getting closer to opening up the limit for upload initially (and soonish) before handling all download scenarios fully.

Level: Powered On

Fair enough, and I apologize for my strong statement, but better communication would help. I'm building some fairly sophisticated apps that are 100% used in a browser on a desktop, not a device. I knew there had to be issues with security, performance, etc. because of that, but the least common denominator approach of functionality based on platform is a problem. Why not let the user determine whether or not they should allow an upload of 100 meg file based on where they plan to deploy (or use) the app. I use PowerApps not to be used on  a mobile device uploading photos, but in a browser uploading documents and other files because I can build rich UI's faster than I would be able to in a framework such as Angular or React. But I have real issues with the way PowerApps works, and it causes me to spend a rediculous amount of time debugging because of issues with data caching, data coercion etc. You update a SQL row from one screen and no matter how many times you execute a 'Refresh' on the connection, you still have the old data in cache. You have to do things like add a timer that refreshes the data source every few seconds to actually get it to work.
Uploading a file the way it's implemented today is a kludge because you have to create a list in Sharepoint (not a document folder) and allow attachments, put a form on your screen connected to that list and push it to Sharepoint. To store the file in a storage account in Azure, I have to create a Flow to copy the file from Sharepoint to the storage account.
So here we are on a thread that was started over a year ago with no better solution in sight, and still with a 10 meg limit. I thought that maybe when Microsoft released the component development kit someone would write a component to upload files using a better approach, but that hasn't happened yet.