I can however tell you that I’ll be spending more effort on this, as I’m working with a very large client on a technical campaign to actively switch heavy Planner users over to Lists. ![]() ![]() However, putting it in the hands of Planner board owners to export / import themselves may not result in a satisfactory timeframe. While doing it programmatically offers considerable benefit for migrating at scale, the amount of effort to make it work correctly with all the variables at that level may be too difficult to get right. There is also the possibility of doing it via Microsoft Graph, possibly even PnP or Microsoft 365 CLI.įind a way that works for you. I’m just not going to figure them out writing this blog piece while my family sleeps and the latest episode of Peacemaker is waiting for me to watch it. There are other steps you could perform in Power Automate to extract / transpose values to make it more complete. I wonder if I could do that from an Excel file…? TakeawayĬould the migration of content be improved over what I’ve demonstrated above? Absolutely! Not all the data I needed, still some manual work to add the missing pieces. So, what did I end up with a the end of this? The “List tasks” and “Get a task” only tell you whether there is a description or not. Can’t get “assigned to” usernames, only user IDs (so we would need to add another action to look them up)Īlso, I needed to add the second action of “Get task details” as it is the only way to expose the contents of the Notes/Description field.“Description” value in the Power Automate action refers to Notes in the Planner task.Unable to obtain bucket name, only its ID.Can only see if label colours are true – not what the value of the renamed label text is (bye-bye categories).Remember a few sentences ago when I said the Planner actions in Power Automate were underwhelming? Well, here’s where they fell short: ![]() Right now, you must be looking at this and thinking that I’ve missed some items – why would I do that!? Well, prepare to now be completely underwhelmed at the Planner actions in Power Automate!Īt a high-level, here’s what our workflow looks like: In my previous blog post comparing Lists to Planner, I highlighted the shortcomings of the Planner triggers in Power Automate. Now that our List is ready, let’s start migrating! Go with the Flow While in Lists we can customise these to be whatever we want, that same is not the case with Planner – so we must align to it.Īdditionally, I had to create the board views with my new list, because the existing “Grouped by priority” and “Grouped by work item progress” pre-date the board view so therefore don’t utilise its functionality. To align with the values used in Planner, we have to make some modifications to the Priority, Progress, and Category columns. To keep things as aligned as possible, I’ve chosen to use the “Work progress tracker” list template. This time we’ll start from a blank list, and we don’t care about the Planner export. We can however create our new board view, so the pain was almost worth it: So if you want these to be assigned to actual people, you’ll need to create new columns and copy the values over. It’s important to know that some of the fields can’t be converted – such as the assigned or created columns cannot be converted from text to people lookup/picker. Remove any other columns you don’t care about, change column types from text to other formats (such as choice), hit “Next”, and a few moments later we have our import. I’d suggest setting the “Task ID” column not to be imported, and that the Task Name column should instead become the Title (as it is a required column, and we don’t need Task ID). (Don’t forget to open the Excel file and define a table before trying to import.) The easiest way to migrate your items would be to simply export your Planner board to Excel, then import it into the List. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |