cancel
Showing results for 
Search instead for 
Did you mean: 

Using patch to depost picture does so with file extension.

Currently when using patch to deposit a photo into Onedrive/Dropbox etc does so without the file extension (.jpg/.png etc) and requires conversion.

 

Sure you know this already but it currently means uploaded none camera media cannot be used outside PowerApps to my knowledge.

 

The syntax I'm using is:

 

Patch(Table2,Defaults(Table2),{image:UploadedImage1.Image})

 

This is from a photo that was uploaded by a user using the "add picture" control.

 

Any thoughts let me know. Is this any different for other connections?

Status: Under Review

This is a known issue. I will keep you posted as this evolves.

 

In the meantime, you may appreciate these articles:

https://powerapps.microsoft.com/en-us/blog/custom-api-for-image-upload/

https://powerapps.microsoft.com/en-us/blog/image-capture-pro-tips/

 

Thank you,

Audrie

Comments
Level: Powered On

I am having this same problem.  Am using similar to yours to save text to a spreadsheet and then deposit the image in a directory.  Again, like you, I am using PATCH.  I am calling the camera.image.  I am also saving data onto OneDrive.  The strange thing is that it doesn't do it from within the dev application - only experienced (so far) when saved from iPhone. 

 

I am really experiencing some frustration with the "glitchyness" of the application. Noted that this thread is silent.  Am wondering if anyone at Microsoft has any ideas, or if they're just as stumped as we are?  (nudge - nudge)

Flow Staff
Status changed to: Under Review

This is a known issue. I will keep you posted as this evolves.

 

In the meantime, you may appreciate these articles:

https://powerapps.microsoft.com/en-us/blog/custom-api-for-image-upload/

https://powerapps.microsoft.com/en-us/blog/image-capture-pro-tips/

 

Thank you,

Audrie

Level: Powered On

Audrie,

 

Unfortunately, there's no ability to address this as a private message, so my response has to go here.  Let me start by saying thank you for your reply. I am glad to know someone reads these posts – even if it is delayed.

 

On the issue itself, this was a known for Microsoft eight-months ago when it was reported by the previous person on this message-chain.  The issue is also discussed on other chains and has always been termed as a glitch that’s pending a fix.  Unfortunately, the continued acceptance of the "glitched" state by Microsoft has left me in a position where I've had no choice but to abandon the idea of using PowerApps to satisfy the needs of these specific clients. In order to meet the requirements of the business, I have deployed a different solution and purchased licenses for a totally different product from another vendor.

 

I realize Microsoft is "strapped" for resources (and that's why it's almost 3 months on the answer) and it's not personally your fault it takes SO long to get a response; however I do feel it necessary to say that the fact that the product has various issues and shortcomings with every answer being another "we'll call you when..." is very frustrating to a user-community that is really looking for some reason to embrace this product.  Please take that for what it's worth and pass it up the chain. 

 

Again, I don’t fault you personally, and do appreciate your reply!  Thanks again.

 

Don