As detailed in my post Workaround for change affecting Patch of Camera.Image to SQL I was having issues with Patching photos (images) from IOS to SQL. I thought it was an SQL / Patch issue. Really it is an issue with the IOS (and Android) players. Instead of having data of data:image/png;base64 they started having /SessionStorage/PApps2011175706348849198.png and Patching that to SQL. Really SQL didn't matter here just the data it was being passed. The new data was useless since it wasn't actual image data.
Today I had a call with Microsoft Escalation Engineer after 6 months of trying. During the call he acknowledged what I was seeing. His answer was I was storing it wrong in SQL. He said I should be using varbinary(MAX) instead of the varchar(MAX) that I have been using for 5+ years. He wondered where I had found that idea. It was from PowerApps: Storing Photos in SQL - Use varchar(max) by Paul O'Flaherty (who seems to have stopped being in PowerApps). Making this change is a lot of work for me since I have 300,000 of existing data.
My question is what are others doing with Photo / Image data when storing to SQL?
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
718
Share
Report
All responses (
Answers (
