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

Retrieving Data URI from an image added via the "Add picture" control

I am trying to submit a photo taken from a PowerApps app to a custom API. There are a number of tutorials written for it, but they all use the built-in camera control, which is very limiting as far as photo-taking goes. It seems that the recent addition of native camera functionality (https://powerapps.microsoft.com/en-us/blog/powerapps-v610/) should work much better, however I am struggling with obtaining the image data from the "Add picture" control.

 

The problem narrows down to the following: when you obtain image data from the Camera control (using the Camera1.Photo property) you get a long Data URI string containing the actual image, it like this:

 

data&colon;image/jpeg;base64<long base64 string follows>

 

When I obtain the image from the "Add picture" control (using AddMediaButton1.Media property) I get a string that looks like this:

 

blob:https://us.create.powerapps.com/dd6409a9-1b09-4ef5-a64b-21c84b16bb54 (if using the web player)
blob:http://127.0.0.1:49428/b7371d5a-bec9-45da-acb4-e2c6a1fefff6 (if using the Android player)

 

So it seems that instead of the actual image content I am getting some kind of a reference to a local blob storage, which is of no use for the purposes of passing it to the API that is expecting the actual image.

 

QUESTION: how can I obtain a proper Data URI string containing the actual image from the "Add picture" control?

27 REPLIES 27

Thanks Claudio for your solution however would it be possible to create a similar example running WebAPI? Also could you provide the full code? 

 

Another question. Where is 

IFormFile coming from?

 

Thirdly, Do you have an ETA when Add Photos functionality similar to the Camera control will be released for GA in PowerApps ?

 

I desperately need it.

 

Thanks

Here are my "using" statements:

 

using System;
using System.IO;
using System.Net;
using System.Net.Http;
using System.Net.Http.Headers;
using System.Text.RegularExpressions;
using System.Threading.Tasks;
using System.Web.Http;

Here are my nuget packages:

 

  <package id="Microsoft.AspNet.WebApi" version="5.2.3" targetFramework="net452" />
  <package id="Microsoft.AspNet.WebApi.Client" version="5.2.3" targetFramework="net452" />
  <package id="Microsoft.AspNet.WebApi.Core" version="5.2.3" targetFramework="net452" />
  <package id="Microsoft.AspNet.WebApi.WebHost" version="5.2.3" targetFramework="net452" />
  <package id="Microsoft.Net.Compilers" version="1.3.2" targetFramework="net452" developmentDependency="true" />
  <package id="Microsoft.Web.Infrastructure" version="1.0.0.0" targetFramework="net452" />
  <package id="Newtonsoft.Json" version="9.0.1" targetFramework="net452" />
  <package id="WebActivatorEx" version="2.2.0" targetFramework="net452" />

Don't worry about the DataAccess class that you highlighted in blue -- that's some internal code specific to my app.

 

 

And to answer your question about IFormFile, I think it's a .Net Core class, I ended up not using it.

Thanks a lot for your quick response. I will try it out and revert back hopefully with good news. 🙂

 

One final question what is this function returning? 

 result = DataAccess.Sharepoint.UploadFile(entityId, saveToPath);

 

Is it a bool field? true or false? 

Yes, bool.

Hi, sorry to bother you but im getting this error when i compile in Azure functions....

 

 

 
2017-07-13T21:14:50.336 Script for function 'HttpTriggerCSharp1' changed. Reloading.
2017-07-13T21:14:50.431 (20,22): error CS0103: The name 'Request' does not exist in the current context
2017-07-13T21:14:50.431 (26,23): error CS0103: The name 'Request' does not exist in the current context
2017-07-13T21:14:50.431 (46,24): error CS0103: The name 'InternalServerError' does not exist in the current context
2017-07-13T21:14:50.431 (49,20): error CS0103: The name 'Ok' does not exist in the current context
2017-07-13T21:14:50.446 error AF001: Your function must contain a single public method, a public method named 'Run', or a public method matching the name specified in the 'entryPoint' metadata property.
2017-07-13T21:14:50.446 Compilation failed.

 

 

 

 

Below is my Azure Function -- HTTP Trigger WebAPI

 

 

using System;
using System.IO;
using System.Net;
using System.Net.Http;
using System.Net.Http.Headers;
using System.Text.RegularExpressions;
using System.Threading.Tasks;
using System.Web.Http;

 

public async Task<IHttpActionResult> UploadImage(int entityId)
{
const string storagePath = @"C:\temp";
var result = false;

try
{
// Check if the request contains multipart/form-data.
if (!Request.Content.IsMimeMultipartContent())
throw new HttpResponseException(HttpStatusCode.UnsupportedMediaType);

var provider = new MultipartFormDataStreamProvider(storagePath);

// Read the form data.
await Request.Content.ReadAsMultipartAsync(provider);

// This illustrates how to get the file names.
var fileData = provider.FileData[0];
if (string.IsNullOrEmpty(fileData.Headers.ContentDisposition.FileName))
throw new HttpResponseException(HttpStatusCode.InternalServerError);

var fileName = fileData.Headers.ContentDisposition.FileName;
fileName = fileName.Trim('"');

var saveToPath = Path.Combine(storagePath, fileName);

//temporarily save the file locally to be later uploaded to Sharepoint
File.Move(fileData.LocalFileName, saveToPath);

result = false; //DataAccess.Sharepoint.UploadFile(entityId, saveToPath);

}
catch (Exception e)
{
return InternalServerError(e);
}

return Ok(result);

}

 

My code runs as a ASP.Net 4.5 Web API method on IIS, which is a different context than Azure functions. Your error seems specific to the latter, so maybe someone with knowledge of Azure Functions can help out.

Anonymous
Not applicable

Hi,

 

Has anyone managed to get this working using an Azure Function / Azure API?

 

I've been scouring the internet attempting to find ways to convert the BLOB format to Data URI / An image byt been very unsuccessful.

 

Any help would be very much appreciated.

 

Thanks again,

Kind regards,

J

I currently use a Flow to upload my image, i perform an action on the byte stream in Azure functions, then pass it to an Azure blob connector to save it in Azure Blob Storage.  I am trying something similiar now with the AddMedia control, but am still just getting the blob address being passed and not the blob itself.

 

Has there been any further developments on this to have it act just like the image control and pass the base64 encoded string for us to work with as that works great?

 

The image control, the pen control, the camera control and the add media should all handle "images" the same way.

More info...

 

I call my Flow with this code from in PowerApps to succesfully upload an image to Azure blob storage: 

UploadDeviceImage.Run(UploadedImage1.Image, "/inventorypictures/TestFolder/", "DeviceImage.jpg")

 

Here is my working Azure function that the flow calls:

using System.Net;
using System.Net.Http;
using System.Net.Http.Headers;

public static async Task<HttpResponseMessage> Run(HttpRequestMessage req, TraceWriter log)
{

    string body = await req.Content.ReadAsStringAsync();  // read image/jpeg;base64
    body = body.Replace("data&colon;image/jpeg;base64,", "");   // remove the header
    var bytes = Convert.FromBase64String(body);           // convert data to bytes
    
    var response = new HttpResponseMessage()
    {
        Content = new ByteArrayContent(bytes),            // write binary out to pass to create blob
        StatusCode = HttpStatusCode.OK,
    };
    response.Content.Headers.ContentType = new MediaTypeHeaderValue("image/jpeg");
    return response;
}

And here is my Flow, which calls the function above and the blob connector:

MicrosoftFlowPic.PNG

 

Pretty simple.  How do i replicate this with the AddMedia control?

 

Based code mentioned in this thread, i created a new Azure function to look like this, but i just get the blog address still:

#r "System.Web"
using System.Web; 
using System.Net;
using System.Net.Http;
using System.Net.Http.Headers;

public static async Task<HttpResponseMessage> Run(HttpRequestMessage req, TraceWriter log)
{
    byte[] bytes = null;

    if (!req.Content.IsMimeMultipartContent())
    {
        return new HttpResponseMessage()
        {
            StatusCode = HttpStatusCode.UnsupportedMediaType
        };
    }        

    var filesReadToProvider = await req.Content.ReadAsMultipartAsync();

    foreach (var stream in filesReadToProvider.Contents)
    {
        bytes = await stream.ReadAsByteArrayAsync();
    }

    var response = new HttpResponseMessage()
    {
        Content = new ByteArrayContent(bytes),            // write binary out
        StatusCode = HttpStatusCode.OK,
    };
    response.Content.Headers.ContentType = new MediaTypeHeaderValue("image/jpeg");
    return response;
}

Any ideas?

 

 

As low code platforms goes, this is a complete fail. If you have to do this much trouble to get the image bits.... as some people say here, the "add picture" control is completely useless this way.

 

 

I have tried a lot of things specified here, but if you have to roll your own api... that's just wrong, that's not low code anymore.

 

Either allow the camera to take high resolution image or make "add picture" easier to use. But this problem is far from solved in my book!

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

Top Solution Authors
Top Kudoed Authors
Users online (2,253)