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

Extracting Array of fields but the field keys are in the JSON values of the key-value pair

I'm attempting to parse a JSON response that has some of its fields hidden away in a nested array. What makes this confusing is the field name is a value in the key-value pair.

 

See below and note the 'fields' array. 

 

 

 

 

 

{
  "data": [
    {
      "id": "1",
      "name": "Fact Sheet Alpha",
      "fields": [
        {
          "name": "Fact Sheet Alias",
          "data": {
            "value": "Different Name",
            "type": "StringValue"
          },
          "dataType": null
        },
        {
          "name": "SyncPolicy",
          "data": {
            "value": "Outbound",
            "type": "StringValue"
          },
          "dataType": null
        },
        {
          "name": "Product Score",
          "data": {
            "value": "Moderate",
            "type": "StringValue"
          },
          "dataType": null
        }
      ],
      "createdAt": "2022-04-19T00:23:50.287331Z",
      "updatedAt": "2022-05-26T20:17:16.170390Z",
      "status": "ACTIVE",
      "qualitySealStatus": "BROKEN",
      "rev": 7
    },
    {
      "id": "2",
      "name": "Fact Sheet Bravo",
      "fields": [
        {
          "name": "Fact Sheet Alias",
          "data": {
            "value": "Yet another name",
            "type": "StringValue"
          },
          "dataType": null
        },
        {
          "name": "SyncPolicy",
          "data": {
            "value": "Inbound",
            "type": "StringValue"
          },
          "dataType": null
        },
        {
          "name": "Product Score",
          "data": {
            "value": "High",
            "type": "StringValue"
          },
          "dataType": null
        }
      ],
      "createdAt": "2022-04-19T00:23:50.287331Z",
      "updatedAt": "2022-05-26T20:17:16.170390Z",
      "status": "ACTIVE",
      "qualitySealStatus": "BROKEN",
      "rev": 7
    },
    {
      "id": "3",
      "name": "Fact Sheet Charlie",
      "fields": [
        {
          "name": "Fact Sheet Alias",
          "data": {
            "value": "Bob",
            "type": "StringValue"
          },
          "dataType": null
        },
        {
          "name": "SyncPolicy",
          "data": {
            "value": "Bidirectional",
            "type": "StringValue"
          },
          "dataType": null
        },
        {
          "name": "Product Score",
          "data": {
            "value": "Low",
            "type": "StringValue"
          },
          "dataType": null
        }
      ],
      "createdAt": "2022-04-19T00:23:50.287331Z",
      "updatedAt": "2022-05-26T20:17:16.170390Z",
      "status": "ACTIVE",
      "qualitySealStatus": "APPROVED",
      "rev": 3
    }
  ]
}

 

 

 

 

 

Conceptually, the data is 

  • id
  • name
  • fields
    • Fact Sheet Alias
    • Sync Policy
    • Product Score
  • etc...

But the JSON above shows that it's not so simple. 

 

I would like to simplify this into a flat schema to

  • id
  • name
  • Fact Sheet Alias
  • Sync Policy
  • Product Score
  • etc...

What I've Tried

The only way I can think to do this is by doing Apply to Each, filtering the array of 'fields' each time for each type of field name, and then consolidating back into a select. However, this is slow and taxing. 

 

The field names will remain consistent, but the order in which they appear in the 'fields' array can easily change (therefore capturing by array index is not feasible). 

 

Ideally I would like to do a Select that has the nested fields defined by expression, but since the nested field names are in the value, not the key, I do not know how to identify them. 

 

Is there a way to accomplish this without doing 'apply to each'? 

1 ACCEPTED SOLUTION

Accepted Solutions

Might want to change the solution 😉

 

See example below that gets what you want.

 

Steps:

  1. Compose your raw data (just for this example)
  2. Compose to get just the array of objects from your raw data
  3. Select to get each of the properties/values in a flat structure

 

The overall flow is below. I'll go into detail on each step after.

grantjenkins_7-1665984033465.png

 

Compose Array Data

This is just a copy of your source data to use in the example.

grantjenkins_2-1665982503059.png

 

Compose Data

This gets just the data array that contains all your objects (removes the object wrapper).

 

outputs('Compose_Array_Data')?['data']

 

grantjenkins_3-1665982590943.png

Select

This extracts out all the properties and values to build up the flat structure you were after. Note that the last three property names are extracted dynamically using the field array indexes 0, 1, 2, and corresponding value for each property, which gets around the ordering issue.

 

The first 7 properties use static names as they are already in a flat structure in the original JSON, and just use the following expression to get the value.

 

item()

 

The last 3 get the name dynamically using the following expressions.

 

item()?['fields'][0]?['name']
item()?['fields'][1]?['name']
item()?['fields'][2]?['name']

 

And corresponding values using the following expressions respectively.

 

item()?['fields'][0]?['data/value']
item()?['fields'][1]?['data/value']
item()?['fields'][2]?['data/value']

 

That way it doesn't matter what order they appear in the original JSON.

grantjenkins_4-1665982701152.png

Sample output of the flat data based on your example data.

 

[
  {
    "Id": "1",
    "Name": "Fact Sheet Alpha",
    "Created At": "2022-04-19T00:23:50.287331Z",
    "Updated At": "2022-05-26T20:17:16.170390Z",
    "Status": "ACTIVE",
    "Quality Seal Status": "BROKEN",
    "Rev": 7,
    "Fact Sheet Alias": "Different Name",
    "SyncPolicy": "Outbound",
    "Product Score": "Moderate"
  },
  {
    "Id": "2",
    "Name": "Fact Sheet Bravo",
    "Created At": "2022-04-19T00:23:50.287331Z",
    "Updated At": "2022-05-26T20:17:16.170390Z",
    "Status": "ACTIVE",
    "Quality Seal Status": "BROKEN",
    "Rev": 7,
    "Fact Sheet Alias": "Yet another name",
    "SyncPolicy": "Inbound",
    "Product Score": "High"
  },
  {
    "Id": "3",
    "Name": "Fact Sheet Charlie",
    "Created At": "2022-04-19T00:23:50.287331Z",
    "Updated At": "2022-05-26T20:17:16.170390Z",
    "Status": "ACTIVE",
    "Quality Seal Status": "APPROVED",
    "Rev": 3,
    "Fact Sheet Alias": "Bob",
    "SyncPolicy": "Bidirectional",
    "Product Score": "Low"
  }
]

 

Optionally, if you wanted to use property names you can then use Parse JSON for each of the objects using the following flat schema.

 

{
    "type": "object",
    "properties": {
        "Id": {
            "type": "string"
        },
        "Name": {
            "type": "string"
        },
        "Fact Sheet Alias": {
            "type": "string"
        },
        "SyncPolicy": {
            "type": "string"
        },
        "Product Score": {
            "type": "string"
        },
        "Created At": {
            "type": "string"
        },
        "Updated At": {
            "type": "string"
        },
        "Status": {
            "type": "string"
        },
        "Quality Seal Status": {
            "type": "string"
        },
        "Rev": {
            "type": "integer"
        }
    }
}

 

 

 

 


----------------------------------------------------------------------
If I've answered your question, please mark the post as Solved.
If you like my response, please consider giving it a Thumbs Up.

View solution in original post

4 REPLIES 4
lbendlin
Multi Super User
Multi Super User

only if you hard code all pointers which is likely not what you want.

 

By the way, I don't see any data.  That JSON is "just" metadata.

Bummer, but understandable. Thanks!

 

Also, much of the data in the example appears to be metadata, but it contains the data I need to sync two environments (e.g., name, id, sync policy, etc.)

Might want to change the solution 😉

 

See example below that gets what you want.

 

Steps:

  1. Compose your raw data (just for this example)
  2. Compose to get just the array of objects from your raw data
  3. Select to get each of the properties/values in a flat structure

 

The overall flow is below. I'll go into detail on each step after.

grantjenkins_7-1665984033465.png

 

Compose Array Data

This is just a copy of your source data to use in the example.

grantjenkins_2-1665982503059.png

 

Compose Data

This gets just the data array that contains all your objects (removes the object wrapper).

 

outputs('Compose_Array_Data')?['data']

 

grantjenkins_3-1665982590943.png

Select

This extracts out all the properties and values to build up the flat structure you were after. Note that the last three property names are extracted dynamically using the field array indexes 0, 1, 2, and corresponding value for each property, which gets around the ordering issue.

 

The first 7 properties use static names as they are already in a flat structure in the original JSON, and just use the following expression to get the value.

 

item()

 

The last 3 get the name dynamically using the following expressions.

 

item()?['fields'][0]?['name']
item()?['fields'][1]?['name']
item()?['fields'][2]?['name']

 

And corresponding values using the following expressions respectively.

 

item()?['fields'][0]?['data/value']
item()?['fields'][1]?['data/value']
item()?['fields'][2]?['data/value']

 

That way it doesn't matter what order they appear in the original JSON.

grantjenkins_4-1665982701152.png

Sample output of the flat data based on your example data.

 

[
  {
    "Id": "1",
    "Name": "Fact Sheet Alpha",
    "Created At": "2022-04-19T00:23:50.287331Z",
    "Updated At": "2022-05-26T20:17:16.170390Z",
    "Status": "ACTIVE",
    "Quality Seal Status": "BROKEN",
    "Rev": 7,
    "Fact Sheet Alias": "Different Name",
    "SyncPolicy": "Outbound",
    "Product Score": "Moderate"
  },
  {
    "Id": "2",
    "Name": "Fact Sheet Bravo",
    "Created At": "2022-04-19T00:23:50.287331Z",
    "Updated At": "2022-05-26T20:17:16.170390Z",
    "Status": "ACTIVE",
    "Quality Seal Status": "BROKEN",
    "Rev": 7,
    "Fact Sheet Alias": "Yet another name",
    "SyncPolicy": "Inbound",
    "Product Score": "High"
  },
  {
    "Id": "3",
    "Name": "Fact Sheet Charlie",
    "Created At": "2022-04-19T00:23:50.287331Z",
    "Updated At": "2022-05-26T20:17:16.170390Z",
    "Status": "ACTIVE",
    "Quality Seal Status": "APPROVED",
    "Rev": 3,
    "Fact Sheet Alias": "Bob",
    "SyncPolicy": "Bidirectional",
    "Product Score": "Low"
  }
]

 

Optionally, if you wanted to use property names you can then use Parse JSON for each of the objects using the following flat schema.

 

{
    "type": "object",
    "properties": {
        "Id": {
            "type": "string"
        },
        "Name": {
            "type": "string"
        },
        "Fact Sheet Alias": {
            "type": "string"
        },
        "SyncPolicy": {
            "type": "string"
        },
        "Product Score": {
            "type": "string"
        },
        "Created At": {
            "type": "string"
        },
        "Updated At": {
            "type": "string"
        },
        "Status": {
            "type": "string"
        },
        "Quality Seal Status": {
            "type": "string"
        },
        "Rev": {
            "type": "integer"
        }
    }
}

 

 

 

 


----------------------------------------------------------------------
If I've answered your question, please mark the post as Solved.
If you like my response, please consider giving it a Thumbs Up.

Genius and exactly the type of solution I was hoping for. Thank you!!

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