cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Using HTTP to get API data from multiple endpoints and consolidating that data into a usable object for SharePoint

Spoiler
UPDATE:  I've figured out a successful method, which I've identified in the thread below.  However, I'm leaving this open to gain feedback on a more efficient or faster approach.

Hi, I've been riding the struggle bus for a few days and could use help.  I feel I'm missing a big-picture issue with how I'm handling my data in Power Automate.

In simple terms:
I just need to add customer names to each of my orderNumber/jobNumber's

The not-so-simple explanation:
Using the HTTP action, I created a flow that GETs a JSON array from my ERP's API.  I can get the majority of the fields I need from an endpoint called "order_routing".  However, that table doesn't have my customer's name.  Therefore, I had to use two HTTP actions and get data from two different tables.

First I get all of my open order numbers from a table called "orders".  Then, I use the "orderNumber" in an apply to each loop to get all of the associated "order_routing" using the same field "orderNumber."  The order number will be something like "200024" and each "order_routing' item has multiple "jobNumber"s that are like "-01, -02, -03, etc."  

So while the "orders" endpoint has "200024", the "order_routing" endpoint may have "200024-01, and 200024-02, and 200024-03."  To further complicate matters, not only will the "order_routing" endpoint return multiple "jobNumber"s, each "jobNumber" has multiple manufacturing steps, all of which come over in the HTTP call.

I'm attempting to use loops and select to get customerDescription, customerCode, and PONumber from the "orders" endpoint and add the data to all "order_routing" items that have the same "orderNumber" from the "order_routing" HTTP call.

Below is my best attempt:

Krickner_2-1704929487592.png

Krickner_3-1704929523056.png

Krickner_4-1704929558974.png

Krickner_5-1704929588367.png

Krickner_6-1704929652536.png

 

I've pasted a successful run below to show why my flow isn't working as intended.  Eventually I need to get this API data in a SharePoint list, but as you can see I didn't make it that far.

Krickner_7-1704929756983.png

Krickner_8-1704929788446.png

 

 




 

 

 

 

 

 

 

 




9 REPLIES 9

Are you certain that 'jobNumber' is a property of the objects in body('Parse_Order_JSON')['Data']? The simplest explanation is it that it isn't. This causes items('Get_Routing_Items_for_Each_Order_Number')?['jobNumber'] to return null. Perhaps you just want to use item()['jobNumber'] instead?

I'll double-check, and try using item()['jobNumber'] 

I changed the job_number value in the Select action to item()['jobNumber'] and got the following error.
"The template language expression 'item()['jobNumber']' cannot be evaluated because property 'jobNumber' does not exist.  

That formula is searching 'orders' not 'order routing'.  Orders only houses customerDescription, customerCode, and PONumber.

Krickner_1-1704980839209.png

 

 

Okay. Then I guess I'm confused why you're doing a Select action if you're not selecting anything from the array that Select action is operating on?

 

Do you know what your SharePoint schema is going to look like? It would be helpful to see a list of your entities and which fields should be under each.

You're probably correct, I've been working on this for three days and I think I've gotten myself turned upside down.  I wasn't using a "Select" originally.  I'll post both schemas below. 

Here is my schema that gets my customerDescription, customerCode, orderNumber, and PONumber:

{
  "type": "object",
  "properties": {
    "Data": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "orderNumber": {
            "type": [
              "string",
              "null"
            ]
          },
          "customerCode": {
            "type": [
              "string",
              "null"
            ]
          },
          "customerDescription": {
            "type": [
              "string",
              "null"
            ]
          },
          "PONumber": {
            "type": [
              "string",
              "null"
            ]
          },
          "status": {
            "type": [
              "string",
              "null"
            ]
          },
          "uniqueID": {
            "type": [
              "integer",
              "null"
            ]
          }
        }
      }
    }
  },
  "required": [
    "Data"
  ]
}

 

Here is my schema that gets "order_routing" data, which is the bulk of my data.  

{
  "type": "object",
  "properties": {
    "Data": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "actualEndDate": {
            "type": [
              "string",
              "null"
            ]
          },
          "actualPiecesGood": {
            "type": [
              "integer",
              "null"
            ]
          },
          "actualPiecesScrap": {
            "type": [
              "integer",
              "null"
            ]
          },
          "actualStartDate": {
            "type": [
              "string",
              "null"
            ]
          },
          "burdenRate": {
            "type": [
              "integer",
              "null"
            ]
          },
          "departmentNumber": {
            "type": [
              "string",
              "null"
            ]
          },
          "description": {
            "type": [
              "string",
              "null"
            ]
          },
          "employeeCode": {
            "type": [
              "string",
              "null"
            ]
          },
          "estimatedEndDate": {
            "type": [
              "string",
              "null"
            ]
          },
          "estimatedQuantity": {
            "type": [
              "integer",
              "null"
            ]
          },
          "estimatedStartDate": {
            "type": [
              "string",
              "null"
            ]
          },
          "itemNumber": {
            "type": [
              "integer",
              "null"
            ]
          },
          "jobNumber": {
            "type": [
              "string",
              "null"
            ]
          },
          "laborRate": {
            "type": [
              "number",
              "null"
            ]
          },
          "lastModDate": {
            "type": [
              "string",
              "null"
            ]
          },
          "leadTime": {
            "type": [
              "integer",
              "null"
            ]
          },
          "machinesRun": {
            "type": [
              "integer",
              "null"
            ]
          },
          "numberMachinesForJob": {
            "type": [
              "integer",
              "null"
            ]
          },
          "operationCode": {
            "type": [
              "string",
              "null"
            ]
          },
          "orderNumber": {
            "type": [
              "string",
              "null"
            ]
          },
          "uniqueID": {
            "type": [
              "integer",
              "null"
            ]
          },
          "partNumber": {
            "type": [
              "string",
              "null"
            ]
          },
          "shift2DefaultEmployeeCode": {
            "type": [
              "string",
              "null"
            ]
          },
          "shift3DefaultEmployeeCode": {
            "type": [
              "string",
              "null"
            ]
          },
          "status": {
            "type": [
              "string",
              "null"
            ]
          },
          "stepNumber": {
            "type": [
              "integer",
              "null"
            ]
          },
          "timeUnit": {
            "type": [
              "string",
              "null"
            ]
          },
          "totalActualHours": {
            "type": [
              "number",
              "null"
            ]
          },
          "total": {
            "type": [
              "number",
              "null"
            ]
          },
          "totalEstimatedHours": {
            "type": [
              "number",
              "null"
            ]
          },
          "totalHoursLeft": {
            "type": [
              "number",
              "null"
            ]
          },
          "vendorCode": {
            "type": [
              "string",
              "null"
            ]
          },
          "workCenter": {
            "type": [
              "string",
              "null"
            ]
          },
          "workCenterOrVendor": {
            "type": [
              "string",
              "null"
            ]
          }
        }
      }
    }
  }
}



So those are the JSON schemas that you're getting back from the API calls. And you're trying to produce a single array in the end? So only a single flat list in SharePoint? Which means you want to add the properties from your parent object, orders, to the child object, order_routing?

Yes.  I really only need "order_routing" data as I'm using the information to create a schedule in SharePoint.  My ERP API gives me everything I need in the "order_routing" endpoint except for 'customerDescription', 'customerCode', and 'PONumber'.  So, I'm trying to figure out a way to add that data to "order_routing" data before bringing it into SharePoint.  Both data sets have an 'orderNumber' field.  

My SharePoint data structure will look like this:

Krickner_5-1704986207666.png

 

 

 



Here is another visual of the data:

Krickner_3-1704985923575.png

 

 



You seem to have the wrong array in your From parameter of your action name "Select"

  1. Change the From parameter of your action named "Select" to be outputs('Parse Order Routing JSON')['Data']
  2. Move the "Select" action outside of the apply to each action
  3. Delete the now empty apply to each action
  4. Inside of the Select, add everything that you want to have in your list. Use item() for Order Routing level properties and items('Get_Routing_Items_for_Each_Order_Number') for all Order level properties. e.g.
    1. items('Get_Routing_Items_for_Each_Order_Number')['PONumber']
    2. item()['jobNumber']
    3. etc.
  5. Outside of your apply to each loop, add a compose action with the formula outputs('Select')
    1. You can delete this action later, this is just for illustrative purposes.

So, now you have an array of arrays containing all of the information. There isn't a good way to flatten arrays out of the box, but there is a janky way we can do it using string manipulation. Create a compose action with the following formula: json(replace(join(outputs('Select'),'@#$%%$@#'),']@#$%%$@#[',','))

 

The reasoning behind the formula:

  1. Join together on what is hopefully a unique string which doesn't occur within the text itself.
  2. Now that we have a string, replace the array breaks with just a comma.
  3. Reconvert back into JSON.

After all of this you can delete your customerDescription variable and actions related to it.

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 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 SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (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. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     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 Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   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 Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

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 (979)