Hello,
I have a JSON object that I need to replace the name of some attributes, a sample JSON object is:
{
"Name": "Kav 338",
"Email": "kav@hotmail.com",
"License": "Mailbox",
"Office": "Sydney",
"SubmittersWorkEmailwillBeUsedToVerifyYou": "kav@gmail.com",
}
I want to use another JSON object as the source for filtering, as an example:
{
"SubmittersWorkEmailwillBeUsedToVerifyYou": "Your email",
"Office": "Location"
{
So basically I want to replace 'SubmittersWorkEmailwillBeUsedToVerifyYou' with 'Your email' and 'Office' with 'Location', in the first JSON object (the name, not the actual value).
Tried an 'Apply to each' with the second JSON object above as input, with the replace() function, but not having much luck... Got errors about self referencing, then an error about data types.
Solved! Go to Solution.
I've got it working using your original Filter JSON. Had to use XPath to get the actual property names.
Below is the full flow. I'll go into each of the actions.
Data (Compose) contains your initial JSON object.
{
"Name": "Kav 338",
"Email": "kav@hotmail.com",
"License": "Mailbox",
"Office": "Sydney",
"Submitter": "kav@gmail.com"
}
jsonData is a string variable that's initially set to the initial JSON data.
Filter (Compose) contains your filter data.
{
"Submitter": "Your email",
"Office": "Location"
}
XML (Compose) converts your Filter JSON data to XML so we can use XPath. It also adds a root element so it's valid XML. The expression used here is:
xml(json(concat('{"root": ', outputs('Filter'), '}')))
Apply to each iterates over each of the items in the Filter object using XPath. The expression used here is:
xpath(outputs('XML'), '//root/*')
Compose uses some more XPath to see if the element names match the filter item, and if so, replace it. The expression used here is:
replace(variables('jsonData'), concat('"', xpath(items('Apply_to_each'), 'name(//*)'), '":'), concat('"', xpath(items('Apply_to_each'), 'string(//*/text())'), '":'))
We then set the jsonData variable to the output of the Compose so eventually it will contain the final output.
Finally, outside (after) the Apply to each, we get use another Compose (Final) to convert the text stored in our jsonData variable to proper JSON using the json expression.
json(variables('jsonData'))
And that's it - you should have your replaced property names in JSON format.
Hey @Kav7
Have you tried using https://learn.microsoft.com/en-us/azure/logic-apps/workflow-definition-language-functions-reference#...
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!
P.S. take a look at my blog here and like & subscribe to my YouTube Channel thanks.
This appears to change the value of the JSON rather than its name? How would I integrate it into a loop so that it does it on each 'replace' in my second JSON object?
Did you have an array of objects you want to do this for, or just a single object?
Also, will the following Filter always just contain those two properties or others? And if the property doesn't exist in the Filter, would it just use the original property name?
{
"SubmittersWorkEmailwillBeUsedToVerifyYou": "Your email",
"Office": "Location"
{
I've built a sample flow that "might" be what you're after. Full flow below. I'll go into each of the actions.
Data is a Compose that contains the base JSON data (for this example).
[
{
"Name": "Abc 123",
"Email": "abc@hotmail.com",
"License": "Mailbox",
"Office": "Brisbane",
"SubmittersWorkEmailwillBeUsedToVerifyYou": "abc@gmail.com",
},
{
"Name": "Kav 338",
"Email": "kav@hotmail.com",
"License": "Mailbox",
"Office": "Sydney",
"SubmittersWorkEmailwillBeUsedToVerifyYou": "kav@gmail.com",
}
]
Filter is a Compose that contains the Property Filters.
{
"SubmittersWorkEmailwillBeUsedToVerifyYou": "Your email",
"Office": "Location"
}
Select takes in the output from Data and converts it to proper JSON using the json expression.
json(outputs('Data'))
The Values in this example are:
item()?['Name']
item()?['Email']
item()?['License']
item()?['Office']
item()?['SubmittersWorkEmailwillBeUsedToVerifyYou']
And the Keys using the Filter object are:
if(empty(outputs('Filter')?['Name']), 'Name', outputs('Filter')?['Name'])
if(empty(outputs('Filter')?['Email']), 'Email', outputs('Filter')?['Email'])
if(empty(outputs('Filter')?['License']), 'License', outputs('Filter')?['License'])
if(empty(outputs('Filter')?['Office']), 'Office', outputs('Filter')?['Office'])
if(empty(outputs('Filter')?['SubmittersWorkEmailwillBeUsedToVerifyYou']), 'SubmittersWorkEmailwillBeUsedToVerifyYou', outputs('Filter')?['SubmittersWorkEmailwillBeUsedToVerifyYou'])
The output from the Select would be:
[
{
"Name": "Abc 123",
"Email": "abc@hotmail.com",
"License": "Mailbox",
"Location": "Brisbane",
"Your email": "abc@gmail.com"
},
{
"Name": "Kav 338",
"Email": "kav@hotmail.com",
"License": "Mailbox",
"Location": "Sydney",
"Your email": "kav@gmail.com"
}
]
Did you have an array of objects you want to do this for, or just a single object?
Nope just a single JSON object that needs words swapped out, though the properties in the JSON input can differ and change.
Also, will the following Filter always just contain those two properties or others? And if the property doesn't exist in the Filter, would it just use the original property name?
Over time I would be adding properties to the filter, so thats why I needed an 'apply to each' loop applied to the filter object and yes if the property doesnt exist in the input JSON it just leaves it as-is.
Because of the dynamic nature, the select portion doesnt really achieve what I am after as its static in relation to the input JSON.
I thought it would be a simple JSON -> Loop through 'filter' properties -> If 'filter' property exists in JSON, use replace() to swap out the data -> Update JSON object
Problem is when selecting JSON properties, it seems you have to specify the name in the expression as the reference which gives you the 'value', but its the name itself that I need as well as the value. Maybe the 'filter' JSON object isn't the appropriate object format for what I am trying to achieve, but its effectively just a lookup table.
What I attempted was something like this:
@Kav7 Are you able to change the filter to a slightly different format to what you currently have? So, keep the initial JSON data as it is.
But change the filter data from:
{
"Submitter": "Your email",
"Office": "Location"
}
To something like the following instead:
[
{
"from": "Submitter",
"to": "Your email"
},
{
"from": "Office",
"to": "Location"
}
]
If you can change the filter object to that format, then I think I've got a working solution. If not, then I'll change my flow slightly using XPath which should still work fine.
I've got it working using your original Filter JSON. Had to use XPath to get the actual property names.
Below is the full flow. I'll go into each of the actions.
Data (Compose) contains your initial JSON object.
{
"Name": "Kav 338",
"Email": "kav@hotmail.com",
"License": "Mailbox",
"Office": "Sydney",
"Submitter": "kav@gmail.com"
}
jsonData is a string variable that's initially set to the initial JSON data.
Filter (Compose) contains your filter data.
{
"Submitter": "Your email",
"Office": "Location"
}
XML (Compose) converts your Filter JSON data to XML so we can use XPath. It also adds a root element so it's valid XML. The expression used here is:
xml(json(concat('{"root": ', outputs('Filter'), '}')))
Apply to each iterates over each of the items in the Filter object using XPath. The expression used here is:
xpath(outputs('XML'), '//root/*')
Compose uses some more XPath to see if the element names match the filter item, and if so, replace it. The expression used here is:
replace(variables('jsonData'), concat('"', xpath(items('Apply_to_each'), 'name(//*)'), '":'), concat('"', xpath(items('Apply_to_each'), 'string(//*/text())'), '":'))
We then set the jsonData variable to the output of the Compose so eventually it will contain the final output.
Finally, outside (after) the Apply to each, we get use another Compose (Final) to convert the text stored in our jsonData variable to proper JSON using the json expression.
json(variables('jsonData'))
And that's it - you should have your replaced property names in JSON format.
That worked, amazing thank you!
I noticed one odd thing though, if I have a space in the filter object replacement like this:
{
"Submitter": "Your email",
"Office": "Big City"
}
In the output "Office" gets replaced with "Big_x0020_City".
Any idea why?
I'm not sure. When I have that I get the following output:
What do you get with "Your email"?
Managed to fix/workaround it by using this expression for the 'attribute' up the chain: replace(xpath(item(), 'name(//*)'), '_x0020_',' ')
Seems to do the job 🙂
I had inserted your flow above into a pre-existing flow (other ones you helped with!) and I think the issue stemmed from some processing after the above flow. This looks odd for example:
But doesn't matter, this works, thanks again 🙂
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