Andrea Rebeccato Added flow source and a diagram link - see here: https://hamsandwich.hashnode.dev/parsing-custom-planner-labels-with-power-automate#heading-flow-source

Andrea Rebeccato I believe I can do both of those. Give me a few days. Will reply back here, either way.

very glad to hear that 👍 Jacob Anderson

Hi there. You'll need to use an expression for both keys - they look like dynamic properties in my screenshot, but they only appear that way after saving and reloading the flow. Locate the image in step 8, right after the sentence with "...might need to zoom in or click..." The two dark rectangles near the bottom contain the expressions I used.

Don't believe I have gotten it to pull anything from SP pages yet... documents only, so far. Perhaps that's a limitation coming out of Graph, for now? Dunno. Certainly not complaining.

I've been tinkering around with CLI for a few months... Had no idea that a third approach for pipeline driven deployment had emerged for Power platform ALM. Figured it was either ADO or github actions, and that was that. I gotta do a better job keeping my eyes open!

Updated. Please let me know if you have any questions on what I added, Kevin. Those labels can be a tough nut to crack and I hope you get it sorted out!

Superb, thank you.

You bet. Saw your note about a week ago - didn't have a chance to reply until now, but the workflow described in this article is still around. I'll add a few more screenshots/details soon.

Solid list. Mastering the art of requirement gathering/interpretation goes a long way too. Same with user-stories. I know that's all a separate discipline, but it can be enormously helpful on smaller projects when you have to flex to cover more roles. I like your blog styling, btw 👍