cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted

Odd Azure DevOps Trigger "Behavior"

The Work Item Created trigger gives access to things like History and a huge number of fields that cant ever have data in them at the time the trigger actually fires while the Work Item Updated provides access to only a fraction of those fields. 

Any ideas on why?

Brian Kennemer
Projectified Consulting
www.projectified.com
brian.kennemer@projectified.com
1 REPLY 1
Community Support Team
Community Support Team

Re: Odd Azure DevOps Trigger "Behavior"

Hi @BrianKennemer,

 

Could you please provide more detail about your issue?

Do you use the trigger "When an item is created or modified" in connector SharePoint?

You mean to have no data in some fields in the output of trigger, is there has no input in these fields when a user updates? If you can share your screenshots of Flow run, we can better assist you.

 

Best Regards,

Community Support Team _ Lin Tu

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Helpful resources

Announcements
thirdimage

Power Automate Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

firstImage

Incoming: New and improved badges!

We've given our badges an overhaul and also added some brand new ones!

fifthimage

Microsoft Learn

Learn how to build the business apps that you need.

sixthImage

Power Platform World Tour

Find out where you can attend!

seventhimage

Webinars & Video Gallery

Watch & learn from the Power Automate Community Video Gallery!

Top Kudoed Authors (Last 30 Days)
Users online (7,369)