cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
wkaper1
Regular Visitor

Bug? Simple CRUD API: strange function signature using PUT function

I have a custom API that does GET, POST, PUT and DELETE actions on a single type of items.
This question / bug report is about the PUT function.
I registered the custom connector and it shows the PUT function correctly as in the below screenshot.

 

Connector_Definition_Put.PNG

As the screenshot shows there are two parameters:
- id
- A record that contains four properties: Title, ToDoID, Priority, Done

If I try to use this function inside PowerApps, it shows me a different signature, as the next three pictures will show.

 

ToDoes_PUT_param1_of_3.PNG

 

PowerApp shows it expects two parameters, called "id" and "Title".
After I add the requested Title as in screenshot 3, it becomes clear that a third parameter is expected which is a record.

 

ToDoes_PUT_param3_of_3_initial.PNG

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Screenshot 3: a Record is expected as a third parameter:
The expected contents of the record are shown between the curly braces, as below:
{ ToDoID: number, Priority: number, Done: Boolean }

My question: why is the "Title" property not inside the curly braces?
That would be consistent with the design of the API as well as consistent with the connectors view of the API.
Can I call it a bug?

This PowerApp works though !
I can update the "Title", if I complete the formula as below (screenshot 4).

 

ToDoes_PUT_param3_of_3_final.PNG

 

If you want to reproduce the "problem", see the details below:

The API is here:
http://entocaretodoapi.azurewebsites.net/
It's public at the moment.

It's swagger file is at:
http://entocaretodoapi.azurewebsites.net/swagger/docs/v1

With best regards,
wkaper1

1 ACCEPTED SOLUTION

Accepted Solutions
v-micsh-msft
Community Support
Community Support

Hi @wkaper1,

 

I don't think this is a bug, it seems this is related with the Todo definition:

  "definitions": {
    "ToDo": {
      "required": [ "Title" ],
      "type": "object",
      "properties": {
        "ToDoID": {
          "format": "int32",
          "type": "integer"
        },
        "Priority": {
          "format": "int32",
          "type": "integer"
        },
        "Title": {
          "maxLength": 50,
          "minLength": 0,
          "type": "string"
        },
        "Done": { "type": "boolean" }
      }
    }
  },

I assume if you remove the "Required " attribute, then the title field should be added into {} under the put method.

 

Regards,

Michael

Community Support Team _ Michael Shao
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

4 REPLIES 4
v-micsh-msft
Community Support
Community Support

Hi @wkaper1,

 

I don't think this is a bug, it seems this is related with the Todo definition:

  "definitions": {
    "ToDo": {
      "required": [ "Title" ],
      "type": "object",
      "properties": {
        "ToDoID": {
          "format": "int32",
          "type": "integer"
        },
        "Priority": {
          "format": "int32",
          "type": "integer"
        },
        "Title": {
          "maxLength": 50,
          "minLength": 0,
          "type": "string"
        },
        "Done": { "type": "boolean" }
      }
    }
  },

I assume if you remove the "Required " attribute, then the title field should be added into {} under the put method.

 

Regards,

Michael

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

Hi @v-micsh-msft,

Thanks for your suggestion. I removed the "required" attribute from the ToDo definition as you suggested. Then re-uploaded the file to PowerApps custom connectors. I clicked "update connector".

Then I opened the PowerApp that uses the API and inspected the formula. It still works and does not show me an error. It is still satisfied getting 3 parameters: first the id, then the Title, then a Record that has just three properties (all four, minus Title).

 

Does the PowerApp still use the old definition of the connector? What should I do to refresh it?

Under the available connections list, delete the old connection of the custom connector, then add a new one.

In PowerApps, under the Add Data Source side, delete the old connection, then click add a new data source, add the corresponding connection there, or you may create a new connection from the Add data source side.

See if this helps.

https://powerapps.microsoft.com/en-us/tutorials/add-data-connection/

 

Regards,

Michael

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

The custom connector was already in the right shape.

I opened the PowerApp, deleted the old connection, then added it again.

Indeed it helps!

I see the REST API formula now as expected:

      ToDoAPI.ToDoesPut( id, { ...} )

 

Just an id and a Record as parameters.

And the Title is now part of the Record.

I still do not understand why he did it differently at first, but I guess I need to study the swagger manuals some more!

 

Thank you for you help!

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,661)