cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Macwin
Resolver I
Resolver I

CustomConnector Error - invalid data from response

image.png

My Custom Connector is actually working. The response is a string, so there shouldnt be a problem with "invalid data"

image.png

 

 

 

{
  "swagger": "2.0",
  "info": {
    "version": "1.0.0",
    "title": "MyAzureFunction"
  },
  "host": "Website",
  "paths": {
    "/api/ConvertMe": {
      "get": {
        "description": "Calls my azure function over https",
        "operationId": "ConvertMe",
        "parameters": [
          {
            "name": "code",
            "in": "query",
            "description": "code",
            "default": "API CODE",
            "type": "string"
          },
          {
            "name": "image1",
            "in": "query",
            "required": true,
            "type": "string"
          },
          {
            "name": "image2",
            "in": "query",
            "required": true,
            "type": "string"
          }
        ],
        "responses": {
          "200": {
            "description": "Successful response",
            "schema": {
              "title": "The response of the api.",
              "type": "string"
            }
          },
          "204": {
            "description": "Successful response",
            "schema": {
              "title": "No Content",
              "type": "string"
            }
          },
          "default": {
            "description": "default",
            "schema": {
              "type": "string"
            },
            "headers": {
              "default": {
                "description": "default",
                "type": "string"
              }
            }
          }
        },
        "summary": "APPCALL"
      }
    }
  },
  "securityDefinitions": {}
}

 

 

 

 

Any ideas how I can fix this problem ? 

 

1 ACCEPTED SOLUTION

Accepted Solutions
v-xida-msft
Community Support
Community Support

Hi @Macwin ,

Do you put the image1 and image2 as Query parameter within the action path in your custom connector?

 

Based on the issue that you mentioned, I think this issue is related to the image1 and image2 as Query parameter in your action path ("ConvertMe") of your custom connnector.

 

Actually, there are some known limits on Query string of HTTP Request, please check the following article for more details:

https://stackoverflow.com/questions/812925/what-is-the-maximum-possible-length-of-a-query-string

https://stackoverflow.com/questions/3091485/what-is-the-limit-on-querystring-get-url-parameters?lq=1

 

If you provided a value which is more than the HTTP Request Query String limit for the image1 and image2 parameter, you would get the error that you mentioned.

 

As an fixed solution, please consider put the image1 and image2 parameter as Request Body parameter rather than Query string parameter within the action path of your custom connector, then re-publish your custom connector, check if the issue is solved.

Note: You also need to change the HTTP Method (operation) from "GET" to "POST".

 

On your side, please consider modify your OpenAPI definition file as below:

{
  "swagger": "2.0",
  "info": {
    "version": "1.0.0",
    "title": "MyAzureFunction"
  },
  "basePath": "/",
  consumes: [],
  produces: [],
  "schemes": [
    "https"
  ],
  "host": "Website",
  "paths": {
    "/api/ConvertMe": {
      "post": {
        "description": "Calls my azure function over https",
        "operationId": "ConvertMe",
        "parameters": [
          {
            "name": "imageBody",
            "in": "body",
            "description": "image body data for converting",
            "schema": {
                        "type": "object",
                        "required": [
                                       "image1",
                                       "image2"
                                    ],
                         "properties": {
                                         "code": {
                                                  "type": "string",
                                                  "default": "API CODE",
                                                  "description": "code"
                                         },
                                         "image1": {
                                                    "type": "string"
                                          },
                                         "image2": {
                                                    "type": "string"
                                          }
                          }
             }
          }
        ],
        "responses": {
          "200": {
            "description": "Successful response",
            "schema": {
              "title": "The response of the api.",
              "type": "string"
            }
          },
          "204": {
            "description": "Successful response",
            "schema": {
              "title": "No Content",
              "type": "string"
            }
          },
          "default": {
            "description": "default",
            "schema": {
              "type": "string"
            },
            "headers": {
              "default": {
                "description": "default",
                "type": "string"
              }
            }
          }
        },
        "summary": "APPCALL"
      }
    }
  },
  "securityDefinitions": {}
}

 

More details about defining Request Body parameter in Open API definition file, please check the following article:

https://swagger.io/docs/specification/describing-request-body/

 

You need to modify your Azure function to receive HTTP POST request from this custom connector rather than GET request. Please remove previous custom connector, then re-add a new one based on above modified OpenAPI definition file, then check if the issue is solved.

 

More details about creating custom connector in PowerApps, please refer to the following article:

https://docs.microsoft.com/en-us/connectors/custom-connectors/define-openapi-definition

 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

9 REPLIES 9
Macwin
Resolver I
Resolver I

It only works if I use a flow for this.

 

Is it possible to do this without using a flow ? 

 

new Error I dont understand.

does this error occurs because the string (base64) is to long for the query request ?
image.png

 

The azure function 

 

 

           string Image1 = req.Query["image1"];
           string Image2 = req.Query["image2"];

      
            if (!string.IsNullOrEmpty(Image1) || (!string.IsNullOrEmpty(Image2)))
            {

               Image1 = Image1.ToString()?.Replace(@"data:image/png;base64,","");
               Image2 = Image2.ToString()?.Replace(@"data:image/png;base64,", "");

                MagickImage _Main = new MagickImage(Convert.FromBase64String(Image1), MagickFormat.Png);
                MagickImage _Overlay = new MagickImage(Convert.FromBase64String(Image2), MagickFormat.Png);

                using (MemoryStream memory = new MemoryStream())
                {
                    Converter.ComebineBitmap(_Main, _Overlay).Write(memory, MagickFormat.Png);
                    memory.Position = 0;


                    log.LogInformation($"Result: {Convert.ToBase64String(memory?.ToArray())}");
                    return Convert.ToBase64String(memory?.ToArray());

                }
            }
            else
            {
                return null;

            }
            

 

 

 

 This is my function which already works on local image.png

 

this error occurs testing with the same base64 in my custom connector.

image.png

or testing in my azure function itself

image.png

Im kinda confused, because there a so many different error message ^^

 

v-xida-msft
Community Support
Community Support

Hi @Macwin ,

Do you put the image1 and image2 as Query parameter within the action path in your custom connector?

 

Based on the issue that you mentioned, I think this issue is related to the image1 and image2 as Query parameter in your action path ("ConvertMe") of your custom connnector.

 

Actually, there are some known limits on Query string of HTTP Request, please check the following article for more details:

https://stackoverflow.com/questions/812925/what-is-the-maximum-possible-length-of-a-query-string

https://stackoverflow.com/questions/3091485/what-is-the-limit-on-querystring-get-url-parameters?lq=1

 

If you provided a value which is more than the HTTP Request Query String limit for the image1 and image2 parameter, you would get the error that you mentioned.

 

As an fixed solution, please consider put the image1 and image2 parameter as Request Body parameter rather than Query string parameter within the action path of your custom connector, then re-publish your custom connector, check if the issue is solved.

Note: You also need to change the HTTP Method (operation) from "GET" to "POST".

 

On your side, please consider modify your OpenAPI definition file as below:

{
  "swagger": "2.0",
  "info": {
    "version": "1.0.0",
    "title": "MyAzureFunction"
  },
  "basePath": "/",
  consumes: [],
  produces: [],
  "schemes": [
    "https"
  ],
  "host": "Website",
  "paths": {
    "/api/ConvertMe": {
      "post": {
        "description": "Calls my azure function over https",
        "operationId": "ConvertMe",
        "parameters": [
          {
            "name": "imageBody",
            "in": "body",
            "description": "image body data for converting",
            "schema": {
                        "type": "object",
                        "required": [
                                       "image1",
                                       "image2"
                                    ],
                         "properties": {
                                         "code": {
                                                  "type": "string",
                                                  "default": "API CODE",
                                                  "description": "code"
                                         },
                                         "image1": {
                                                    "type": "string"
                                          },
                                         "image2": {
                                                    "type": "string"
                                          }
                          }
             }
          }
        ],
        "responses": {
          "200": {
            "description": "Successful response",
            "schema": {
              "title": "The response of the api.",
              "type": "string"
            }
          },
          "204": {
            "description": "Successful response",
            "schema": {
              "title": "No Content",
              "type": "string"
            }
          },
          "default": {
            "description": "default",
            "schema": {
              "type": "string"
            },
            "headers": {
              "default": {
                "description": "default",
                "type": "string"
              }
            }
          }
        },
        "summary": "APPCALL"
      }
    }
  },
  "securityDefinitions": {}
}

 

More details about defining Request Body parameter in Open API definition file, please check the following article:

https://swagger.io/docs/specification/describing-request-body/

 

You need to modify your Azure function to receive HTTP POST request from this custom connector rather than GET request. Please remove previous custom connector, then re-add a new one based on above modified OpenAPI definition file, then check if the issue is solved.

 

More details about creating custom connector in PowerApps, please refer to the following article:

https://docs.microsoft.com/en-us/connectors/custom-connectors/define-openapi-definition

 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

thank you very much.

but I´m still kinda confused how to edit my azure function for receiving req.body.

do you have an example in c# for request body?

Hi @Macwin ,

Yeah, please check and see if the following blog would help in your scenario:

https://softwareengineering.stackexchange.com/questions/245921/how-to-structure-rest-api-service-tha...

https://dotnettutorials.net/lesson/post-method-in-web-api/

 

Please consider take a try with above solution, then modify your Azure function, then check if the issue is solved. If the solution I provided above is helpful in your scenario, please consider click "Accept as Solution" to identify this thread has been solved.

 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

unfortunately the links does not help on my scenario :S

I dont know how to get my image objects to my function 

 

 

        [FunctionName("ConvertMe")]
        public static async Task<string> RunAsync
            ([HttpTrigger(AuthorizationLevel.Function, "post", Route = null)] HttpRequest req, ILogger log)
        {
            log.LogInformation($"Received a Request");
            ConvertMe Converter = new ConvertMe();


            var content = await new StreamReader(req.Body).ReadToEndAsync();
            Imagebody imagebody = JsonConvert.DeserializeObject<Imagebody>(content);

                MagickImage _Main = new MagickImage(Convert.FromBase64String(imagebody.image1), MagickFormat.Png);
                MagickImage _Overlay = new MagickImage(Convert.FromBase64String(imagebody.image2), MagickFormat.Png);

                using (MemoryStream memory = new MemoryStream())
                {
                    Converter.ComebineBitmap(_Main, _Overlay).Write(memory, MagickFormat.Png);
                    memory.Position = 0;
                    log.LogInformation($"Result: {Convert.ToBase64String(memory?.ToArray())}");
                    return @"data&colon;image/png;base64," + Convert.ToBase64String(memory?.ToArray());
                }
        }
    }

    public class Imagebody
    {
        public string code { get; set; }
        public string image1 { get; set; }
        public string image2 { get; set; }
    }

 

 

image.png

 

Ok the function works 

  public static class Function1
    {
        [FunctionName("ConvertMe")]
        public static async Task<string> RunAsync
            ([HttpTrigger(AuthorizationLevel.Function, "post", Route = null)] HttpRequest req, ILogger log)
        {
            log.LogInformation($"Received a Request");
            ConvertMe Converter = new ConvertMe();


            var content = await new StreamReader(req.Body).ReadToEndAsync();
            Imagebody imagebody = JsonConvert.DeserializeObject<Imagebody>(content);

                MagickImage _Main = new MagickImage(Convert.FromBase64String(imagebody.image1), MagickFormat.Png);
                MagickImage _Overlay = new MagickImage(Convert.FromBase64String(imagebody.image2), MagickFormat.Png);

                using (MemoryStream memory = new MemoryStream())
                {
                    Converter.ComebineBitmap(_Main, _Overlay).Write(memory, MagickFormat.Png);
                    memory.Position = 0;
                    log.LogInformation($"Result: {Convert.ToBase64String(memory?.ToArray())}");
                    return Convert.ToBase64String(memory?.ToArray());

                //@"data&colon;image/png;base64," + 
            }
        }
    }

    public class Imagebody
    {
        public string code { get; set; }
        public string image1 { get; set; }
        public string image2 { get; set; }
    }}

image.png

 

but if I use it on my custom connector Im receiving a 401 error.

 

image.png

Hi @Macwin ,

The HTTP 401 error means that you have faced a Authorization issue with custom connector. On your side, please consider create a new connection to your custom connector from your PowerApps when testing your custom connector, then check if the issue is solved.

 

Also please make sure you have specified proper Authentication way within your custom connector.

 

Best regards, 

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

does this 401 error occurs because I dont use my function key not as query anymore ? he is in the request body now.

If this is the problem how do I have to call this in my function and do I need to change the swagger like this? 
image.png

 

and Im going to update my security after this Environment works 🙂 

 

edit:// my  flow is working now

image.png

 

what are the next step to improve the perfomance ? I mean 22 seconds is to much ^^

 

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

Users online (833)