I have been attempting to follow @DamoBird365 guide of Bulk Import Tasks into Planner.
Bulk Import Tasks into Planner - DamoBird365
All is working and I have further customised the flow to my needs, except for the HTTP Request which I have put down to the change of it becoming a V2 version? I don't fully understand what this action is actually doing so not sure what to change to fix it.
Has anyone successfully got an HTTP Request V2 to change the flag Show on Card so the checklists are visible when created or have a solution for this to work?
What is the problem that you have? Is it giving you an error?
I've never used this exact process before, but your HTTP request looks like it matches the example you linked to.
The only difference will be the Body. I think your body might need to be formatted. Sometimes the amount of blank spaces will determine if it works or not.
So instead of Body:
{ "previewType": "checklist" }
Copy in the body with the line breaks:
{
"previewType": "checklist"
}
You can also change the view from editing the flow in Co-Pilot designer to the Switch to Classic Designer which will look the same as the example you used.
Hi wskinnermctc,
Thanks for your reply. The error information may have been helpful to include!
I have made the change as you suggested and still get the same error.
I haven't felt the need to switch to the classic designer as I don't believe that will achieve anything differently. Unless I am mistaken on that?
Here is a link that is documentation about HTTP requests using GRAPH REST API for Update Task Details
It is kind of an outline that shows how REST request are to be sent when updating planner tasks.
The connector for Office 365 Groups - Send an HTTP Request V2 shouldn't function any different than the previous Send an HTTP request [DEPRECATED] action that was used in the instructions example. The "V2" just means that it is the second version of the action in power automate that replaced a previous action.
So basically, just because your example instructions are using the action "Send an HTTP request" and you are using "Send an HTTP request V2" this should not be the reason you have an error.
Ah thank you for the error photo.
The issue is not with the HTTP request. The issue is with the "Update Task Details". The action "Update Task Details" is not completing properly, so the HTTP request is getting skipped.
You need the action "Update Task Details" to have a Is Successful result in order for the HTTP request to function.
(Unfortunately there is a difference between what works in Co-Pilot and what works in Classic. It is really hard to tell if that is the issue here. There should not be a difference; however, some things don't work when formatted in Co-Pilot.
I don't know if that is your problem; I thought you were concerned about being able to match your flow with the instructions and switching the view would help see any differences.)
Really after seeing the error photo, I can't tell if it is the Update Task Details or something even further up the flow. It could be that Update Task Details is getting skipped because a previous action is not functioning correctly.
Either way, it is not the HTTP request that is causing the problem. It is a previous action in the flow.
Thank you for the larger photo.
I don't know much about your entire flow, but those gray minus circles means the action did not run. I think that your Condition is returning false. You can put a Compose in the False side of the Condition and re-run the flow to see if that side is running.
Comparing what I see from your flow and the instructions, it looks like you may be duplicating steps?? I see the instructions has a Scope named "CreatingTasks" and then it has steps in it. Your flow also has a Scope of "CreatingTasks" but then has a Condition followed by the actions to create a task.
Are you duplicating the steps to create a task?
Ok I added a compose into the false and that isn't being run.
I now have a different error though and that is a BadRequest on the HTTP Request.
The condition is definitely returning true otherwise the tasks wouldn't be being created in the planner which they are.
I'm not duplicating steps but I have customised this flow, the Condition is checking to see if a category matches a user input from the trigger input, if it doesn't match I don't want the task created and this is working as I expect it to.
@nevjmac Thank you for the photo. You are correct about not duplicating steps. Sorry I'm not used to looking at the Co-Pilot view. I see that this is everything within the Scope. I was thinking there was a separate scope CreateTasks above that was minimized. My mistake.
Ok, well this is good that it works all the way down to the HTTP request; so at least we finally see that it is the issue.
I'm thinking the best way to check this will be process of elimination to determine what is wrong with the HTTP request.
The first thing I would do is to make sure the Id being used in the Uri is correct.
To check this:
The HTTP request is a GET type using the task Id. So if this is correct, it will pull some data from the task in the outputs.
Hi wskinnermctc,
I have made the change and that gets a NotSpecified error.
I am wondering if it is easier that someone that knows what this HTTP request is doing tries to replicate this part of my flow and has any luck in getting it working?
Solved: Re: Update task detail - Show on card - by Send HT... - Power Platform Community (microsoft....
Interestingly I am having the similar issue as updates on this thread
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