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

Extracting a substring from parsed JSON data in a Loop

I'm stumped on this one, folks.

I am taking JSON data from an online form, parsing it, and converting it into a .csv for import. I have built and tested a flow that works exactly as needed - almost. 

The online form gives users the option to enter information for anywhere from 0 to 10 children (family law intake). So, the JSON can contain data for 0 to 10 children. Incoming data for the fields contains either a six-or-eight-character Code, and then an explanation (it's in a drop-down on the online form). I need to export only a substring of that data (either the left 6 or 8 characters) into the .csv for import.

 

Problem is, I can't use Initialize Variable to do this within a loop (that will run x times, where x = 0 to 10).

Is there a way to substring just the raw parsed JSON data so I only grab the characters I need for inclusion in the variable table I have created for the data (prior to export to .csv)? I have tried to use the 'substring' expression, but it won't even let me select the variable I need from within the sub-data for "CHILDINV" - I'm stuck.

Child Data Loop.JPG

27 REPLIES 27

No, we want a consistent header line, even if there is no data in the field below. Makes it easier that way.

@Paulie78 's solution looks a bit less daunting tbh, but I'm stuck on understanding how he is referencing the fields.

 

I now see that doing it the way I was doing it, via variables, is long and cumbersome - this "compose" function makes it more of a one-shot schema creation. As much as I hate to throw away what I have done already, I like that it moves all of the expressions and fiddling with the data into one place.

I have lots to learn on this stuff, it's only the first of many I am going to have to create. Thanks so much for your patience and efforts thus far.

If you need help building it reach out via private message and will get you started off.

It does produce two rows, perhaps I copied the wrong scope. Will check in a moment. 

Absolutely, @ArchieGoodwin, here's a solution which produces all the rows, all the headers, and the full 10 kids.

 

I'll admit that were this me I'd space out the logic a bit more so that others won't be blinded by the long expressions on show. One of the main things I try to show folks in a work environment that Power Automate makes an office less reliable on Jon/Janey and their wizard excel formulas. As soon as you start sprinkling long 'formula' everywhere here, anyone taking over the management of it might still be a bit taken aback.

 

If I were to do that here, I might make the two sides of that union in the CSV separate object variables then reference them.


Solution

This solution is transferrable if you want to apply it to more than one array in the original data.

finally.jpg

@Paulie78 thanks for the help, and for the range fiddle, too! I had originally done ten fields that long way, and thought that there *had* to be a way to get it done with less typing. 😅


Code

kidsVAR

This just counts the number of kids, and subtracts it by one. This saves overcomplicating the multiple if() statements in the Select action.

 

 

sub(length(variables('jsonInputVAR')?['body']?['CHILDINV']), 1)

 

 

SelectKidsData

In the 'From' field this uses a trick that Paulie taught me elsewhere, the range() function. So it iterates through 10 items, regardless.

 

 

range(0, 10)

 

 

In the 'Map' 'key' fields (left), this uses some basis logic looking at the current item() number in the range, and adds 1. This provides your child number.

 

 

add(item(), 1)

 

 

In the 'Map' 'value' fields (right), this uses a simple condition. If the current item() number is greater than the number returned in the kidsVAR variable, then it places nothing ('') in the field, otherwise it picks the child data that is correspondent to the current item() number. It looks like more than it is. 👍

 

 

if(greater(item(), variables('kidsVAR')), '', variables('jsonInputVAR')?['body']?['CHILDINV'][item()]['Id'])

if(greater(item(), variables('kidsVAR')), '', variables('jsonInputVAR')?['body']?['CHILDINV'][item()]['C1NAME'])

if(greater(item(), variables('kidsVAR')), '', variables('jsonInputVAR')?['body']?['CHILDINV'][item()]['C1BD'])

if(greater(item(), variables('kidsVAR')), '', variables('jsonInputVAR')?['body']?['CHILDINV'][item()]['Gender'])

if(greater(item(), variables('kidsVAR')), '', variables('jsonInputVAR')?['body']?['CHILDINV'][item()]['C1LEGAL'])

if(greater(item(), variables('kidsVAR')), '', variables('jsonInputVAR')?['body']?['CHILDINV'][item()]['C1PHYS'])

if(greater(item(), variables('kidsVAR')), '', variables('jsonInputVAR')?['body']?['CHILDINV'][item()]['C1VISIT'])

if(greater(item(), variables('kidsVAR')), '', variables('jsonInputVAR')?['body']?['CHILDINV'][item()]['FIELD8'])

if(greater(item(), variables('kidsVAR')), '', variables('jsonInputVAR')?['body']?['CHILDINV'][item()]['ItemNumber'])

 

 

Create CSV Table

This one is basically constructing an array for the Create CSV Table action to make its data from. Don't forget to place the square brackets around it in the 'From' field:

 

 

union(removeProperty(variables('jsonInputVAR')?['body'], 'CHILDINV') , json(replace(join(body('SelectKidsData'), ', '), '}, {', ',')))

 

 

The union() function is usually used to join two arrays together, but it works with objects, too, so the main thing here is ensuring that the child data is represented as an object instead of an array, after the previous Select action has done its thing.

 

So, in the second section of that union function this is done by:

  1. Using a join() function to join the separate children items together in a string value.
  2. Once they're in the string, they're still actually separated by curly brackets, so the replace() function removes the ones separating the children '}, {', and puts a normal comma in their place.
  3. Then finally the json() function makes that all readable by the union otherwise it would error thinking it's just a string.

 

The first part is getting all the non-child data by simply using the removeProperty() function to strip the CHILDINV data out of the original object.

 

Additional Arrays

To apply this to other fields in the original JSON just requires a few tweaks. Let's look at the potential for the DOCUMENTS array field to need it.

  1. Add a branch after the input.
  2. Initialise a docsVAR integer variable in the new branch to count the items in DOCUMENTS.
  3. For the Select copy the original and edit it to save time to SelectDocsData.
  4. Change the letters either side of the add(item(),1) expressions in the key fields to make your document headers.
  5. Edit each value to point to DOCUMENTS instead of CHILDINV, the new docsVAR for the counts, and change the referenced field names.
  6. Finally, bridge the branches with the CSV:

 

union(removeProperty(removeProperty(variables('jsonInputVAR')?['body'], 'CHILDINV'), 'DOCUMENTS') , json(replace(join(body('SelectKidsData'), ', '), '}, {', ',')) , json(replace(join(body('SelectDocsData'), ', '), '}, {', ',')))

 

If there is no set limit to the documents, then take the docsVAR and add 1 to it for the other side of the range() expression.

 

EDIT - I've tested this on ten children ... and they're all still alive to tell the tale!

One teeny tiny problem. I can't figure out how to put the SUBSTRING instruction into the map. I keep getting "invalid expression" errors; how do I grab only, say, the first 6 characters in C1LEGAL for example? I know it's probably a syntax issue.

Where would you squeeze in the SUBSTRING?

Also - I really only need the CHILD output from this, because I don't carry across all the fields, only ones I need. But, if I try to create a CSV table from OUTPUT, there are a bunch of extra commas in there that I don't need.

Thoughts?

(sorry, was weirdly scared to come back in case it wasn't a good solution!)

 

I'm glad all is good, @ArchieGoodwin  ... apologies if I'd misunderstood. But given your responses after Paulie mentioned ensuring there were 10 kids each time, I thought the extra data was what you were after there.

 

Those extra commas in the example of 4 children are the empty children 5-10. (or empty fields in the base data)

 

If you wish to have only what's there (for the kids, at least), that's more simple, just change the SelectKidsData to be like in my OG solution with the ['body']?['CHILDINV'] source, item()['ItemNumber'] for the numbered keys, and reference the fields accordingly (item()?['Id']) on the value side. You can delete the count, too.

02 - Kids Data OG.jpg

 

 

SUBSTRING

This part is thankfully easy, I'll give you two ways you can do it and hopefully the first is the way that it can be done easiest.

 

Method One - Add An Extra Select Value

This assumes that you will always have "TEXT - TEXT", meaning that there is always that space-hyphen-space, there.

 

On the 'Key' side it will be however you like, as before. I labelled mine as C3LGLSh (where the 3 is the expression).

 

On the 'Value' side it will be:

 

if(greater(item(), variables('kidsVAR')), '', first(split(variables('jsonInputVAR')?['body']?['CHILDINV'][item()]['C1LEGAL'], ' - ')))

 

You are splitting the "CLIENT - sdfkjhsfgldihsd fg" text on that ' - ', and then with the array that returns you take the first item. A safer bet might be to split on just the hypen, and then wrap the first() in a trim() expression.

 

This ensures that you are always going to get whatever text is there, even if it's longer than 6 characters.

 

Method Two - Substring

If you really have to use substring, then this would work with the otherwise same setup as the first method:

 

 

if(greater(item(), variables('kidsVAR')), '', substring(variables('jsonInputVAR')?['body']?['CHILDINV'][item()]['C1LEGAL'], 0, 6))

 

 

It definitely works, just tested, I just feel that the split+first (+trim!) method is going to be better data capture long term.

 

 

KIDS ONLY!

If you only need the CHILD output, then you can junk the union() expression and just keep the second half of it. So, non-code view thats:

[

  json(repl...)

]

In the json() you'd have:

 

json(replace(join(body('SelectKidsData'), ', '), '}, {', ','))

 

 

NONSENSE STUFFS 😉

There's a few ways to go about the unimportant fields.

  1. Filter - Filter out stuff you don't want, try to use branching if you can to keep the original data available when needed.
  2. Handle Externally - Keep the extra fields, and handle the relevant output on the other end. You then have that data when you need it.
  3. Layered Property Removal - removeProperty() layers to remove the fields you don't currently need.
  4. Explicit Select Fields - Use Paulie's setup to be very exact precisely which field and where you're taking data from.

#2 would be the most accepted/normal way. For example if you were querying an API for data, you would take what you get, and use what you need.

 

With #3 you just layer it up, like this:

 

removeProperty(removeProperty(variables('jsonInputVAR')?['body'], 'CHILDINV'), 'DOCUMENTS')

 

That would supply an object with all the original fields except the CHILDINV, and DOCUMENTS, fields. 

 

Here's one more image to assist, this one has all 10 kids included, obviously:

extra bitz.jpg

 

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!

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.    

Summer of Solutions | Week 3 Results | Win free tickets to the Power Platform Conference

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  

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 (3,608)