I have a variable that is constructing Update plannerTaskDetails api call with a plannerChecklistItems resource type . However when I look at how the variable is put in the api call it is a string instead of an array and I'm not sure why.
Below the relevant steps in creating the variable
Initialising;
because there is a for each loop running through plan the variable gets emptied each time it loops using a set variable;
each checklist item is appended to the matrix
Then the variable is used in the body of an API call
{
"previewType": "checklist",
"checklist": @{variables('Subtakenmatrix')}
}
When I look at the actual body it is generated as below, where instead of JSOn objects ;
"body": {
"previewType": "checklist",
"checklist": [
"613f9ed0-8a19-4222-af66-a326e838c8f1:{\n \"@odata.type\": \"microsoft.graph.checklistItem\",\n \"orderHint\": \"11056\",\n \"title\": \"Installatie(s) aangemaakt\",\n \"isChecked\": False\n}",
"9854b267-23d7-4cc8-bf35-0782940271e2:{\n \"@odata.type\": \"microsoft.graph.checklistItem\",\n \"orderHint\": \"35845\",\n \"title\": \"Object aangemaakt\",\n \"isChecked\": False\n}"
]
}
Resulting in 400
Any idea how to get the correct json syntax in the API call?
Thank you in advance
Solved! Go to Solution.
@v-mengmli-msft is right!
I should have had a closer look at your flow 😔
The issue is, that you have an @ in your property name "@odata.type" this has a special meaning in the action's input and therefore must be hidden.
Try with an expression:
string('@odata.type')
Here the actual data comes from the parse JSON (in your case items('Toepassen_op_elke_checklistitem'))
[
{
"id": "123",
"title": "Just a test 1",
"isChecked": true
},
{
"id": "234",
"title": "Just a test 2",
"isChecked": false
}
]
Compose creates the object to add
Compose 2 creates the new complete object
Set variable set the variable to this new object
Compose 2
addProperty(
variables('SubtakenMatrix'),
guid(),
outputs('Compose')
)
Output of Compose 2
Your "checklist" is an array of strings.
These strings are similar to JSON but have some errors. Have you done any string manipulations to it?
To convert these strings back to JSON, the following repairs are required:
json(
concat(
'{"',
replace(
replace(
item(), ':{', '":{'
),
'False', 'false'
),
'}'
)
)
This is just an indication of what to look out for.
I don't recommend adding this to your flow, but fixing the creation of this array in your flow 😉
Hey rimmon, thanks for the reply and suggestion!
When I attempt to use {} I get an error which translates to;
The input parameters of the Apply_to_each_bucket_from_the_template operation contained one or more invalid expressions. Correct the invalid expressions for the input parameters of the Apply_to_each_bucket_from_template operation.
However I can put a [ ] in the same positions as you marked it will still convert the whole variable into a string i.e.
"checklist": [
"[ \"27125c36-ec19-45ec-acd5-ce0dd0a01570\" : {\n \"@odata.type\": \"microsoft.graph.checklistItem\",\n \"orderHint\": \"18401\",\n \"title\": \"Pand van voor \",\n \"isChecked\": False\n}]",
"[ \"daa1ea2f-9b5d-41a3-bb76-8b40dfcdd5e0\" : {\n \"@odata.type\": \"microsoft.graph.checklistItem\",\n \"orderHint\": \"59252\",\n \"title\": \"Asbestinventarisatierapport\",\n \"isChecked\": False\n}]"
]
Hey @Chriddle , thanks for the reply!
I came to the same conclusion, I'm very much trying to fix the variable so that it stays JSON! .. I dont do any string manipulations in the flow (all steps are shared in the original post). I find it so odd that when I put the variable in a JSON it says the variable type is an Array but when I input the variable it outputs as a string.
My current concern is the part where I 'wipe' the array using a set array variable with the value [] that this somehow breaks the variable type?
.. I cant set it to {} howver..
I saw another post that suggested updating it with a different empty array variable but that seems like even more steps for something that should be straightforward
@v-mengmli-msft is right!
I should have had a closer look at your flow 😔
The issue is, that you have an @ in your property name "@odata.type" this has a special meaning in the action's input and therefore must be hidden.
Try with an expression:
string('@odata.type')
Oh fantastic, this was very helpfull indeed, thank you very much @Chriddle - I've seen the @{output} variables and shouldve guessed.. I will remember this lesson well!
I have one final issue to contend with, the array is no longer being shown as a giant string, however it is still outputting between [ ] , see:
"body": {
"previewType": "checklist",
"checklist": [
{
"1701011f-1100-41b6-9c68-26319260a6fe": {
"orderHint": "18401",
"title": "Pand van voor ",
"isChecked": false,
"@odata.type": "microsoft.graph.checklistItem"
}
},
{
"792e1dd2-6d86-4908-a81d-97ffc16b4535": {
"orderHint": "59252",
"title": "Asbestinventarisatierapport",
"isChecked": false,
"@odata.type": "microsoft.graph.checklistItem"
}
}
]
}
Now I tried to work around this by calling the variable with a [0] but it will only output the first object of the array then (without the [ ] though!)
Any ideas how to get all the objects in the array without the [ ] output into the body?
I'm fairly certain it has something to do with how i'm 'resetting' to an empty array at each loop (set variable to [ ] )
but I'm unsure how else to reset to an empty array (Note: it wont accept { } )
This expression can do the conversion:
first(
json(
replace(
string(variables('Subtakenmatrix')),
'},{',
','
)
)
)
and the result should look like this:
{
"1701011f-1100-41b6-9c68-26319260a6fe": {
"orderHint": "18401",
"title": "Pand van voor ",
"isChecked": false,
"@odata.type": "microsoft.graph.checklistItem"
},
"792e1dd2-6d86-4908-a81d-97ffc16b4535": {
"orderHint": "59252",
"title": "Asbestinventarisatierapport",
"isChecked": false,
"@odata.type": "microsoft.graph.checklistItem"
}
}
However, a probably cleaner way to achieve this would be not to use an array variable, but an empty object and addProperty().
I just learned that there is a better way:
Hey @Chriddle , your earlier json() replace() function indeed works, thanks a bunch!
And I like the double @! Thanks for updating me with your find .. I think also prefer that escape over the string function (I'm learning tremendously from both!)
I'm also intrigued by your object variable mention and have questions about using the object() variable
1: what step would one use to invoke the addProperty() function? Is this where the compose step would be used?
2; In the case of the plannerchecklistItem where there object is a value (the guid) holding multiple values, would you addProperty() that in a single run or would you do it in multiple steps? and use the output of the first addPropert();
assuming the object variable is x for a single run you'd do?
addProperty(x, "guid()", {
string('@odata.type'): "microsoft.graph.plannerChecklistItem",
"title": "body('blabla)?['Title']",
"isChecked": @if(items('Toepassen_op_elke_checklistitem')['value']['isChecked'], true, false)
})
Thank you once more for your time and responses, it's most appreciated
Here the actual data comes from the parse JSON (in your case items('Toepassen_op_elke_checklistitem'))
[
{
"id": "123",
"title": "Just a test 1",
"isChecked": true
},
{
"id": "234",
"title": "Just a test 2",
"isChecked": false
}
]
Compose creates the object to add
Compose 2 creates the new complete object
Set variable set the variable to this new object
Compose 2
addProperty(
variables('SubtakenMatrix'),
guid(),
outputs('Compose')
)
Output of Compose 2
I'm learning a lot from you @Chriddle , thank you once more for taking the time!
Really appreciate it. I ended up having to redo the whole flow due to there being a difference between the planner tasklist and the project tasklist (also in the new Task management in teams..
But it's going a lot easier this time around (I like to think I'm getting the hang of it! 😉 )
Have a great weekend!
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