Dublicates when creating a workitem

[Amalie1]

Hi,

I am using power automate to create a flow that will create a work item in Azure DevOps. I am currently suing the 

'When a new email arrives in a shared mailbox (V2)' to send in the attachment the work item should be created from. Then I 'apply to each' and 'create work item', connecting it to Azure DevOps. The flow works, however when I send the email and the work item is created, it creates 2 different items. One that is correctly created and one for the "image". How do I get it not to create two items when sending an email?

[Expiscornovus]

Hi @Amalie1,

If you want to create just one work item you could place the create work item directly after the when a new email arrives in a shared mailbox (v2) trigger action. This way it will be only executed once.

Btw, is there any reason/requirement why you are using an apply to each action? 

[Amalie1]

Hi @Expiscornovus 

Thank you for your reply!

I have tried creating the flow without the 'apply to each', but every time I add the input, it automatically creates the 'apply to each'. I cannot seem to find a way around this.

[Expiscornovus]

Hi @Amalie1,

You can use expressions to avoid this. Can you share a screenshot of which fields you are using in your Create a work item action?

This way I can help you out with a specific example for this.

[Amalie1]

[Expiscornovus]

Hi @Amalie1,

Below is an example.

To be clear, I am using an index [0] to get the first attachment and refer to the name value by using the below expression:

triggerOutputs()?['body/attachments'][0]['name']

[Amalie1]

Thank you so much! I will try that

[Amalie1]

Hello again, I have tried using the expression both in the Title and Description, however I was given an error when trying to run it. And now I cannot choose an expression anymore and how put it in manually.

Below I have attached the expressions I have used, and also what my options are when clicking the box. Does it look right to you?

[Expiscornovus · Accepted solution]

Hi @Amalie1,

Normally a popup window should appear to add the expression.

If in your case that does not happen we can try a workaround. Try and directly copy/paste the below into the field instead.

That should recognize it as an expression because of the '@{' and '}' around the expression

@{triggerOutputs()?['body/attachments'][0]['name']}

[Amalie1]

Hi @Expiscornovus 

I figured out why it looked so weird, I just had to get it from my laptop and up to a bigger screen.

I managed to get it to work without creating duplicates, thank you so much!