Hello,
I am working on a PC Request Notification Flow that runs when a PC request has been edited. My goal is to include a list of what changed in the email. Overall, it is going well, but there are 2 standard fields I don't need to put into the email which are "Modified" and "PCFormVersion". I would like to remove those 2 fields from the list that is included in the notification email. I'm getting an error on my second Select action that states "The 'from' property value in the 'select' action inputs is of type 'Object'. The value must be an array." I'm still new to PowerAutomate so I'm having a hard time figuring out how to adjust the flow. Can you help me?
Here is the Output from the first Select step so you can see what is being returned (this step is not broken).
Here are the flow steps. The last step labeled "Select - Remove" is the one that is throwing an error.
Here are the expressions I am having trouble with in text format:
json(replace(string(outputs('Select')),'Modified','PCFormVersion'))
removeProperty(removeProperty(item(),'Modified'),'PCFormVersion')
Hopefully, only small adjustments are needed. Thanks in advance for your help!
Teresa
Solved! Go to Solution.
To remove items from an array use Filter array instead of Select. Put the expression @And(not(equals(item(),'Modified')),not(equals(item(),'PCFormVersion'))) in the advanced editor.
The problem is the JSON( ) expression returns a JSON object, not the array a Select action uses.
But my bigger question is why are you trying to do that replace?
If you use the standard Select table format, you can list the column/field names on the left & their corresponding values on the right. Then if you just don’t include Modified or PCFORM… then they won’t be included in the output.
If you need to let it be variable with different possible columns or fields, then why not just use a Compose action & use replace( ) from there?
To remove items from an array use Filter array instead of Select. Put the expression @And(not(equals(item(),'Modified')),not(equals(item(),'PCFormVersion'))) in the advanced editor.
Thank you both for your advice. I really appreciate it. @takolota, if I understand your question correctly, the reason I can't pick out certain fields using the Select action is that the results from "Get changes for an item or a file" varies. I only wish to include fields in the email that have changed. @WillPage I incorporated your expression so I thank you very much.
Here is the current version of the flow. Seems like a lot of steps to get to what I want so let me know if there is a more efficient way to consolidate the steps. Also, if you scroll down further to the email screenshot, you can see it is not very elegant. The internal SharePoint column names are displayed. Is there a way to show the Display Names instead? My Display Names have spaces between words.
Email screenshot:
@tagustin You can get the display names of the columns using the "Send an HTTP request to SharePoint" action.
The request path is _api/Web/Lists/GetByTitle('List Name')/Fields?$select=staticname,title
If the schema is unlikely to change, just hit the URL in a logged in browser (e.g https://myorg.sharepoint.com/sites/mysite/_api/Web/Lists/GetByTitle('List Name')/Fields?$select=staticname,title where myorg is your SharePoint domain, sites/mysite is the path to the site containing the list and List Name is the Display Name of the list or library.
Hit it once in the browser and paste the result into a compose action. Now do another Filter array and input outputs('Compose')?['value'] with the condition body('FilterArray') contains item()?['StaticName]. Replace outputs('Compose') with whatever action contains the output from that HTTP action, whether you do that each flow run or you put it in a compose.
Now the result of that action should contain an array of the relevant columns with the two properties, StaticName and Title, so to get the Display Names of these, do a Select and in there, press the small T icon on the right of the key-value input boxes and in there put the expression item()?['Title']. You can then run the join over the output of that to get a string of the Display Names of the columns.
Thank you Will. I will give this a try tomorrow morning (Wed) and let you know how it works out.
Kind regards,
Teresa
Hi Will,
Sorry for the delay in getting back to you. I had an app meeting with IT that resulted in a lot of great feedback to incorporate into the app so I've been working on that before adjusting the flow since the changes involved adding extra fields. I think I have everything dialed in now so I'm hoping to be able to work on implementing your solution for display names tomorrow. Thanks again for your advice. I really appreciate it!
Teresa
Hello Will,
I finally got a chance to work on this on Saturday. I added a Send an HTTP request step per your instructions and ran the flow. I didn't get any errors and I can see that promising results are being returned.
I wasn't completely sure what you meant 7 lines down where you say "Hit it once in the browser and paste the result into a Compose action." Thinking you might have meant for me to run the flow and paste the body of the Flow Run Outputs section into a Compose action, I went in that direction. The ComposeOutputs text is very long so I'm just showing the beginning and end to help us troubleshoot the error I am getting in the FilterArrayOutputs step.
Here is the error I am getting at the FilterArrayOutputs step. I did make changes to the PC Request Form so I'm not sure why it is returning 'Null'.
Here are the expressions I entered into the step. The expression in the notes section is what I entered into the From field. When I enter body('FilterArrayOutputs') in the Condition body, the expression does not save as it says the step cannot reference itself. This is why I tried (body('ComposeOutputs') instead.
Thinking it might be a flow step order issue, I've tried placing the Send an HTTP step both above and below the Get changes for an item step. It throws the same Null error either way. What should I try next?
Thank you again for your help. I hope you have a nice weekend!
Teresa
Try changing that label in the compose from “d” to “body”
You may also need to add more to your expression to get your desired piece of data.
Check the start of this video that explains some of expressions for calling JSON data: https://youtu.be/C52brz28poU
Also I’m not sure if you’re trying to use the static results in a compose here or if you need dynamic results.
Thank you for the advice, but even after changing the "d" to "body" I am getting the error message "Bad Request. The 'from' property value in the 'query' action inputs is of type 'Null'. The value must be an array."
To answer your question about whether I need dynamic results. In these steps, I'm trying to get the Display Names whether or not the column was changed. If I can get these results back, I can then cherry pick out the ones where the column was changed with the Select action.
Teresa
Hello,
I'm still trying to solve the issue of how to come up with the display names, but wanted to let you know that I will be off the computer from Fri-Tues as I have family coming to the house for a visit. If you have any more thoughts on what I should adjust I would love to hear them! Have a great weekend! Teresa
“You may also need to add more to your expression to get your desired piece of data.
Check the start of this video that explains some of expressions for calling JSON data: https://youtu.be/C52brz28poU”
I don’t know what specific part you’re trying to get your data from as you didn’t show it all.
But it looks like it may be several layers deep in your JSON & array structure. You’ll need to create an expression that manually parses through those parts to get to your specific data.
Hello,
Thank you for the advice. I think you are right in saying I need an expression to get to the data I need. I tried watching Reza's video, but couldn't figure out how to make it work for me. Here is a sample of the outputs I am getting from my 'ComposeTitles' step.
{
"d": {
"results": [
{
"__metadata": {
"id": "https://fortive.sharepoint.com/sites/TEKCSOEmployees/_api/Web/Lists(guid'e9bae1f6-5440-414f-93c9-f9862ed0e1e2')/Fields(guid'1d22ea11-1e32-424e-89ab-9fedbadb6ce1')",
"uri": "https://fortive.sharepoint.com/sites/TEKCSOEmployees/_api/Web/Lists(guid'e9bae1f6-5440-414f-93c9-f9862ed0e1e2')/Fields(guid'1d22ea11-1e32-424e-89ab-9fedbadb6ce1')",
"type": "SP.Field"
},
"StaticName": "ID",
"Title": "ID"
},
Here are the Outputs from my 'FilterArrayGetChanges' step.
Here the expressions entered into the Filter array fields. The flow fails at this step. The error message is "The 'from' property value in the 'query' action inputs is of type 'Null'. The value must be an array."
How can I manipulate what is returned from the 'FilterArrayGetChanges' step so I can compare it to what is returned in the 'ComposeTitles' step? I really appreciate you hanging in there with me as I think this solution will not only benefit myself, but others in the Community as well.
Thank you!
Teresa
You need to clean up the output of the FilterArrayGetChanges action so you have just the column's internal name. To do this, add a select action and put the output of the filter array into its input, then click the T icon on the right to switch from key-value inputs to raw, and add the following expression into it: substring(item(),2,sub(indexOf(item(),':true'),4))
The result of this will look like
[
"GridLocation",
"DeviceType",
"DeviceName"
]
Now, add an Apply to each and inside that, add a filter array. The input of the filter array is outputs('ComposeTitles')?['d']?['results'] and the thing to filter for is items('Apply_to_each') is equal to item()?['StaticName'] where Apply_to_each is whatever you called the apply to each loop but with spaces substituted for underscores (or find it in dynamic content, usually down the bottom of the list).
Now add a compose and do first(body('Filter_array'))?['Title'] to get the string value of the column display name, also assuming your filter array above is called Filter array.
After the loop, you can reference that compose in another compose: Simply outputs('Compose') as an expression where Compose is the name of the compose inside your loop. The outer compose will be an array of all the values of the Title properties from the list metadata, which you can now use in your email/notification/approval or whatever it is you're doing with it.
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