cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
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
www.projectified.com
brian.kennemer@projectified.com
1 REPLY 1
Highlighted
Community Support
Community Support

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
FirstImage

Microsoft Ignite 2020

Check out the announcement of Power Platform content at Microsoft Ignite!

thirdImage

Experience what's new for Power Automate

Join us for an in-depth look at the new Power Automate features and capabilities at the free Microsoft Business Applications Launch Event.

firstImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

Top Solution Authors
Top Kudoed Authors
Users online (5,088)