How to i extract certain fields from this to Sharepoint? Issue is I cant use line #'s because sometimes fields are missing so line number might change.
[
" ",
"NOL #:",
"560286",
"Offense Date:",
"Aug 10 2023 5:09PM",
"Intersection:",
"ETEXTTEXT St @ TEXTTEXT",
"Vehicle Information",
"ETEXTTEXT ID:",
"26771",
"License Plate:",
"TEXTTEXT",
"Make:",
"JEEP",
"Model:",
"PATRIOT",
"Agency Code:",
"TEXTTEXT",
"Account No:",
"Vehicle Owner",
"Name:",
"TEXTTEXT",
]
Solved! Go to Solution.
Below is how I'd likely build the flow using some XPath expressions.
See full flow below. I'll go into each of the actions.
JSON is a Compose that contains your data.
XML is a Compose that converts your data to XML so we can use XPath. The expression is below.
xml(json(concat('{"root": { value:', outputs('JSON'), '}}')))
Initialize variable data creates a variable called data of type Object and sets it to an empty object using opening and closing curly braces {}.
Apply to each iterates over each of the items that contain a period : These are your property names. The expression used is below.
xpath(xml(outputs('XML')), '//root/value/text()[substring(., string-length(.)) = ":"]')
Item is a Compose that appends the property name and value using the following expression.
addProperty(
variables('data'),
replace(item(), ':', ''),
xpath(xml(outputs('XML')), concat('string(//value[contains(./text(), "', item(), '")]/following-sibling::*[1]/text())'))
)
Set variable data sets the new value of the variable data to the output from Item. This will eventually contain all the properties and their values in an object for you to use.
The variable data would now contain the following:
{
"NOL #": "560286",
"Offense Date": "Aug 10 2023 5:09PM",
"Intersection": "ETEXTTEXT St @ TEXTTEXT",
"ETEXTTEXT ID": "26771",
"License Plate": "TEXTTEXT",
"Make": "JEEP",
"Model": "PATRIOT",
"Agency Code": "TEXTTEXT",
"Account No": "Vehicle Owner",
"Name": "TEXTTEXT"
}
To access the individual items you can use the following expressions.
variables('data')?['NOL #']
variables('data')?['Offense Date']
variables('data')?['PROPERTY NAME']
Here is the easiest way I can come up with at the moment, I was thinking there'd be a way to search an array for a value and return the associated array index, but I can't figure that out (don't even know if it exists.. @Expiscornovus , @wskinnermctc , @Pstork1 - you guys know of anything?). So, I found another way.
I've pasted your text into a string variable called strData.
Above, I'm doing the following:
Initialize Variable - arrKeys: Creating an array of all of the named types of things I want to retrieve. I've only put 3 in as an example, just Make, Agency Code, Intersection.
Compose - Remove Quotations: I'm just replacing all " with blank, so it's cleaner.
Apply to Each: I'm aiming it at our array of keys. On each cycle, it will select a different one to evaluate.
Compose - Split on First Key: Here, I'm splitting the cleansed data by the first value from the array ("Make:")
Find text position - Ending Value Comma: Here, I'm selecting the last() item from our split text, and then I'm searching for the first comma (as that tells us the end of the value associated with our key.)
Substring - Extracted Value: Then, again on the last() part of that split array, we're getting a substring - starting from 0 - the amount of characters that the "find text position" told us.
In this scenario, that last Substring returns "JEEP".
Now you have a few options. You could build another array, (ie, use "Append to an Array", and then do "Current Item":"Substring - Extracted Value" -- it would give you a full, clean array to input to SharePoint.)
OR, you could create a variable for each type - ie, txtMake, txtAgency, txtIntersection, etc, and select the variable by using a matrix to identify the right one, or something like that. Depends what you need to do with it.
I answer questions on the forum for 2-3 hours every Thursday!
Below is how I'd likely build the flow using some XPath expressions.
See full flow below. I'll go into each of the actions.
JSON is a Compose that contains your data.
XML is a Compose that converts your data to XML so we can use XPath. The expression is below.
xml(json(concat('{"root": { value:', outputs('JSON'), '}}')))
Initialize variable data creates a variable called data of type Object and sets it to an empty object using opening and closing curly braces {}.
Apply to each iterates over each of the items that contain a period : These are your property names. The expression used is below.
xpath(xml(outputs('XML')), '//root/value/text()[substring(., string-length(.)) = ":"]')
Item is a Compose that appends the property name and value using the following expression.
addProperty(
variables('data'),
replace(item(), ':', ''),
xpath(xml(outputs('XML')), concat('string(//value[contains(./text(), "', item(), '")]/following-sibling::*[1]/text())'))
)
Set variable data sets the new value of the variable data to the output from Item. This will eventually contain all the properties and their values in an object for you to use.
The variable data would now contain the following:
{
"NOL #": "560286",
"Offense Date": "Aug 10 2023 5:09PM",
"Intersection": "ETEXTTEXT St @ TEXTTEXT",
"ETEXTTEXT ID": "26771",
"License Plate": "TEXTTEXT",
"Make": "JEEP",
"Model": "PATRIOT",
"Agency Code": "TEXTTEXT",
"Account No": "Vehicle Owner",
"Name": "TEXTTEXT"
}
To access the individual items you can use the following expressions.
variables('data')?['NOL #']
variables('data')?['Offense Date']
variables('data')?['PROPERTY NAME']
I made an assumption and took a slightly different approach. I assumed that the key for the value was always the value immediately prior to it in the list that ended with ':'. If that is valid to assume then this is the process I used.
1) Clean the input from email by replacing all the newline characters using decodeUriComponent('%0A').
2) Split the result on the commas to get an array of the values in the list
3) Use that array in an apply to each. Check the current item to see if it is contains a ':'. If it does then store that value in a variable called currentKey for the next loop. If it doesn't then check to see if the currentKey is blank. If its not then append the currentKey and the current Item value to an Array variable. YOu'll also have to clean up additional characters like quotes and colons from the result.
4) The output of the loop will give you an array of values where the keys were supplied as previous values. You can then run that through a Parse JSON to have access to the individual keys.
This will use only one apply to each rather than one apply to each for each key.
Thanks folks...I'm going to try each solution this weekend and get back
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!
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
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.
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