Showing results for 
Search instead for 
Did you mean: 
Kudo Kingpin
Kudo Kingpin

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
Community Support
Community Support

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

MPA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group


Experience what’s next for Power Virtual Agents

See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.

New Super Users

Meet the Power Automate Super Users!

Many congratulations to the Season 1 2021 Flownaut Crew!

Power Platform ISV STudio

Power Platform ISV Studio

ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.

Top Solution Authors
Top Kudoed Authors
Users online (18,231)