Creating multiple tags in DevOps

[Valentino1]

Hello everyone, here i have just a basic, create a work item, what i also need to do is put multiple tags into that work item.

Does anyone know what am i supposed to be putting into the URI, also to note, i my tags are dynamic so they are different, depending on the item that triggered the flow in the first place. Every item has a set of values that i want to have as tags in the DevOps, so i cant put hardcoded values as tags.

[Expiscornovus · Accepted solution]

Hi @Valentino1,

I guess you are retrieving the tags from another column from your SharePoint list item? 

In that case you can use a Select to only retrieve those choice values. With a join function you can join them together in a format which is suitable for DevOps (with a ; separator). You can use that in your PATCH request, https://learn.microsoft.com/en-us/rest/api/azure/devops/wit/work-items/update?view=azure-devops-rest...

Below is an example

1. Add a Select to only retrieve the values of your choice column (as an array).

Don't forget to switch the Map field of the Select action to text mode (one column instead of two) with the t button on the right side before you add the Tag value column to it.

2. The HTTP request action uses

URI 

@{variables('Project')}/_apis/wit/workitems/@{outputs('Create_a_work_item')?['body/id']}?api-version=7.1-preview.3

Headers

{
  "Content-Type": "application/json-patch+json"
}

Body

[
 {
    "op": "add",
    "path": "/fields/System.Tags",
    "value": "@{join(body('Select'), ';')}"
  }
]

[Valentino1]

Yes sorry, this is the screenshot i meant to post.

[Expiscornovus]

Hi @Valentino1,

Is it the domains column?

In that case just replace the tag column in my example by the domains column and the tag value column by the domains value column in the Select action for my proposed solution.

[Valentino1]

I have another question with the "Initialize variable", what do i put into that variable? Sorry for the dumb question, im just sort of new to this.

[Expiscornovus]

Hi @Valentino1,

Yes, no problem at all.

It is a string variable to store the name of my Azure DevOps project. This way I don't have to type it in the URI of my HTTP request action as well 😁

[Valentino1]

Ahhh okay, makes sense. I put mine as the Title of my sharepoint item that triggered the flow, thats correct right? Or is that project supposed to be static, because its a project in devops, or something ?

[Expiscornovus]

Hi @Valentino1,

That would be something static, since it is your project name in Azure DevOps.

[Valentino1]

Hey, i also have a follow up question you will probably know how to solve.

https://powerusers.microsoft.com/t5/Building-Flows/Sending-emails-to-multiple-people/td-p/2562849/ju...

This is my post, in which i use the same list and the same flow, just for a different thing, if you could take a look it would be greatly appreciated!

[Valentino1]

Hmmm, this is an error im getting when i try to trigger the flow, the HTTP request

[Expiscornovus]

Hi @Valentino1,

Can you share a screenshot what you used in the HTTP request action?

Did you copy/paste what I shared earlier in my example flow or did you type things yourself? (URI, Headers and Body snippets)?

[Valentino1]

Yeah i just copy and pasted. I only manually selected the Project and Id in the URI.

[Expiscornovus]

Hi @Valentino1,

Have you tried editing and testing the same HTTP request action from the classic designer, to see if that makes a difference?

Can you also share a screenshot of the inputs section of the failed HTTP request action? (Below is a similar example of my working test run for comparison).

[Valentino1]

So I tried running in the classic designer, same thing happened...

[Expiscornovus]

Hi @Valentino1,

It looks like you have not configured the Select action correctly. The values in the body still show two columns

{"HR":""}

Instead of just

HR

This suggests that you haven't switched the Map field of to Select action to text mode (single column). Can you correct that?

Below is an example gif which demonstrates this switching (click on it to see it in higher resolution).

[Valentino1]

So it failed again, but if you look at the second picture, when i changed the map it created an "apply to each" and it ran the same tags that were supposed to be there 5 times each one

[Valentino1]

also funny thing is, it created the work item in devops, but without tags, as it probably cant write 5 same tags for each different tag

[Expiscornovus]

Hi @Valentino1,

Yes, it won't like that duplicate tag input in the HTTP request, that is definitely causing your new error.

Can you please remove the apply to each from your setup? 

If it still adds the apply to each whenever you try adding your domains and domains value fields to the Select action you could also try adding them as expressions instead.

From field (Domains)

triggerOutputs()?['body/Domains']

Map field (Domains Value)

item()?['Value']

[Valentino1]

So, it wouldnt let me take it out from the loop, but now im getting this as an error

[Expiscornovus]

Hi @Valentino1,

I see you have added the expressions as plain text. Can you add them via the Expression tab instead?

From

Map