You’re offline. This is a read only version of the page.
Hi guys,
I would like to create a flow that automatically generates a work item on Azure DevOps using elements from a SharePoint list. In SharePoint, I've set up a list with columns such as ID, issue title, description, status, priority, created date, and logged by. While the flow successfully handles fields like title, description, and date, it encounters issues with columns like status, priority, and logged, where users can select options like high, low, or normal.
The problem arises because the runtime expects these values to be converted into integers or int32. How can I resolve this and ensure the flow works smoothly?
If anyone could provide hints or screenshots illustrating the solution, it would be greatly appreciated! 😄
Hi @BlackMamba,
For that part you would have to collect the attachment content and use a couple of HTTP requests to upload it and relate it to a work item in DevOps.
@abm, has a nice video about this approach, https://www.youtube.com/watch?v=Ivdj6Gf_K-M That video uses email attachments as a source, but you could use the same HTTP request approach for SharePoint attachments.
Thank you so much! That totally solved my problem. But I have one more question. I created two columns, first one (associated files)- where the user can add an attachment and another one (images) to upload image to the sharepoint list element. How do I connect this to azure so that these files automatically appear there?
Hi @BlackMamba,
In that case you might be able to use the priority/id property of your choice field. That id field does starts counting with 0 instead of 1. So, you would have to add 1 to it to be able to use it in the priority field of a Azure DevOps work item.
Try something like below.
1. This sample assumes you have the below order in your choice field.
2. When you trigger the flow you can see in the outputs that each choice corresponds with a number as well, the id field.
3. You can reuse that id field in your Priority field of the work item creation. Only gotcha is that you need to add 1 because the DevOps priority list does not start at 0 but at 1, unlike SharePoint choice values.
Share
Report
All responses (
Answers (add(triggerOutputs()?['body/Priority/Id'],1)
Hi @Expiscornovus !
I have used a column with a choice type, so the user can choose from 4 options: critical, high, normal, low.
I would like it to work in such a way that after selecting, for example, the critical option in priority in sharepoint, the corresponding number in azure would appear - that is, 1.
Hi @BlackMamba,
What type of columns did you use for priority and status in your list? Single line of text?
In that case you could use an int function to convert the value to a number.
int(triggerOutputs()?['body/Priority'])
Below is an example of that approach.
#1
Michael E. Gernaey
200
Super User 2025 Season 1
#2
David_MA
192
Super User 2025 Season 1
#3
stampcoin
177
