cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
ArchieGoodwin
Advocate I
Advocate I

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
ArchieGoodwin
Advocate I
Advocate I

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. 

eliotcole
Super User
Super User

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?

eliotcole
Super User
Super User

(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

Update! June 13th, Community Ambassador Call for User Group Leaders and Super Users

Calling all Super Users & User Group Leaders   UPDATE:  We just wrapped up June's Community Ambassador monthly calls for Super Users and User Group Leaders. We had a fantastic call with lots of engagement. We are excited to share some highlights with you!    Big THANK YOU to our special guest Thomas Verhasselt, from the Copilot Studio Product Team for sharing how to use Power Platform Templates to achieve next generation growth.     A few key takeaways: Copilot Studio Cookbook Challenge:  Week 1 results are posted, Keep up the great work!Summer of Solutions:  Starting on Monday, June 17th. Just by providing solutions in the community, you can be entered to win tickets to Power Platform Community Conference.Super User Season 2: Coming SoonAll communities moving to the new platform end of July We also honored two different community members during the call, Mohamed Amine Mahmoudi and Markus Franz! We are thankful for both leaders' contributions and engagement with their respective communities. 🎉   Be sure to mark your calendars and register for the meeting on July 11th and stay up to date on all of the changes that are coming. Check out the Super User Forum boards for details.   We're excited to connect with you and continue building a stronger community together.   See you at the call!

Copilot Cookbook Challenge | Week 2 Results | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge is a great way to showcase your creativity and connect with others. Plus, you could win tickets to the Power Platform Community Conference in Las Vegas in September 2024 as an amazing bonus.   Two ways to enter: 1. Copilot Studio Cookbook Gallery:  https://aka.ms/CS_Copilot_Cookbook_Challenge 2. Power Apps Copilot Cookbook Gallery: https://aka.ms/PA_Copilot_Cookbook_Challenge   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: https://aka.ms/Copilot_Challenge_EarlyBirds if you would like to be entered in the 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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  @Dhanush 2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a   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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. Kasun_Pathirana1. ManishSolanki2. cloudatica2. madlad3. n/a3. SpongYe4. n/a4. n/a5. n/a5. n/a

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

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**

Celebrating the June Super User of the Month: Markus Franz

Markus Franz is a phenomenal contributor to the Power Apps Community. Super Users like Markus inspire others through their example, encouragement, and active participation.    The Why: "I do this to help others achieve what they are trying to do. As a total beginner back then without IT background I know how overwhelming things can be, so I decided to jump in and help others. I also do this to keep progressing and learning myself." Thank you, Markus Franz, for your outstanding work! Keep inspiring others and making a difference in the community! 🎉  Keep up the fantastic work! 👏👏 Markus Franz | LinkedIn  Power Apps: mmbr1606  

Your Moment to Shine: 2024 PPCC’s Got Power Awards Show

For the third year, we invite you, our talented community members, to participate in the grand 2024 Power Platform Community Conference's Got Power Awards. This event is your opportunity to showcase solutions that make a significant business impact, highlight extensive use of Power Platform products, demonstrate good governance, or tell an inspirational story. Share your success stories, inspire your peers, and show off some hidden talents.  This is your time to shine and bring your creations into the spotlight!  Make your mark, inspire others and leave a lasting impression. Sign up today for a chance to showcase your solution and win the coveted 2024 PPCC’s Got Power Award. This year we have three categories for you to participate in: Technical Solution Demo, Storytelling, and Hidden Talent.      The Technical solution demo category showcases your applications, automated workflows, copilot agentic experiences, web pages, AI capabilities, dashboards, and/or more. We want to see your most impactful Power Platform solutions!  The Storytelling category is where you can share your inspiring story, and the Hidden Talent category is where your talents (such as singing, dancing, jump roping, etc.) can shine! Submission Details:  Fill out the submission form https://aka.ms/PPCCGotPowerSignup by July 12th with details and a 2–5-minute video showcasing your Solution impact. (Please let us know you're coming to PPCC, too!)After review by a panel of Microsoft judges, the top storytellers will be invited to present a virtual demo presentation to the judges during early August. You’ll be notified soon after if you have been selected as a finalist to share your story live at PPCC’s Got Power!  The live show will feature the solution demos and storytelling talents of the top contestants, winner announcements, and the opportunity to network with your community.  It's not just a showcase for technical talent and storytelling showmanship, show it's a golden opportunity to make connections and celebrate our Community together! Let's make this a memorable event! See you there!   Mark your calendars! Date and Time: Thursday, Sept 19th Location: PPCC24 at the MGM Grand, Las Vegas, NV 

Tuesday Tip | Accepting Solutions

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   To enhance our collaborative environment, it's important to acknowledge when your question has been answered satisfactorily. Here's a quick guide on how to accept a solution to your questions: Find the Helpful Reply: Navigate to the reply that has effectively answered your question.Accept as Solution: Look for the "Accept as Solution" button or link, usually located at the bottom of the reply.Confirm Your Selection: Clicking this button may prompt you for confirmation. Go ahead and confirm that this is indeed the solution.Acknowledgment: Once accepted, the reply will be highlighted, and the original post will be marked as "Solved". This helps other community members find the same solution quickly. By marking a reply as an accepted solution, you not only thank the person who helped you but also make it easier for others with similar questions to find answers. Let's continue to support each other by recognizing helpful contributions. 

Users online (2,290)