Cannot update Azure Boards user story using Flow Designer

[Erik Gunther2]

I'm creating a Flow Designer workflow that will update an Azure Boards user story using the Azure DevOps Spoke. To my amazement, it appears that you can only enable the Additional Fields section by manually inputting a valid Work Item ID value. When I drag and drop an input data pill, the Additional Fields section remains disabled. The implication here is that this paid spoke only supports hard coded work items. Is this really how this works? Has anyone been able to use this to update the Work Item ID at runtime using a data pill?

If this is the case, then I'll need to figure how to use the Graph spoke. 

Thanks in advance for any help. 

[Elias Beylouny]

Hi Jagrati

Do you have a solution on that issue?

thanks

Elias

[jehova_honey]

Additional Fields is a dynamic input which depends on Work Item ID. It uses Work Item ID to call another action which gets the list of additional fields. If you use data pill for Work Item ID, it doesn't have any value while creating/updating flow to fetch the additional fields. 
You need to use a data pill for additional fields input also. 
Refer to this KB for the solution to the same problem in Jira spoke. https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0818189 

[jehova_honey]

Drag and drop any string field with an encoded query on top of the additional fields, even if it's greyed out.
Use the 'Generate Encoded Query' action from the Utility Actions Spoke to form the encoded query.
Refer to the attached screenshot for guidance on providing input values (key-value pairs) for the above action. Ensure you provide the correct names for the keys, which can be found by running the 'Get Editable Fields' action.

[Tim Deniston]

It's stunning that this isn't documented anywhere except in the Now Support KB article. 

Before I found this Community post, I had been manually writing a string with the text, like...

"System.Title=" + fd_data.trigger.current.short_description + "^System.State=New"

It worked, but using the Generate Encoded Query action is much simpler. The action is really just building name-value pairs and then concatenating them as a string in the same format as an encoded query.

Once the Generate Encoded Query action is in place, you can drag it from the right pane onto the Additional Fields field in your flow. The UI doesn't indicate that it's going to work, but it ended up accepting the drag-and-drop step for me.

I had been receiving an error "Bad Request. The current operation ended in state: ERROR. Detail: Error: (Process Automation.1d657e3dc7bcc01024f6612827c2601c; line 9)" before using the Generate Encoded Query action. 

Thank you, @jehova_honey, for pointing out this Now Support article.