Unanswered

Troubleshooting flow to trigger email when Sharepoint list item status changes - wrong ID

(0) Share

Report

Posted on by billicatons

Hi everyone,

First post as I am a relative newcomer to Power Automate with lots to learn. I have built a simple flow to send an email notifying users when a sharepoint list item has a column updated (the actual scenario is to trigger a 'shipment complete' email to a requester when the sharepoint list status on their request is changed to 'complete')

My flow works, but for one thing. The triggered email includes the ID of the request ('Your request IDXXX is complete'). But the ID displayed in the triggered email is the ID of the *previous* Sharepoint list item, not the one whose status is updated.

All the other fields in the email are shown correctly, so I can't work out why the wrong ID is being included. Any tips very gratefully received. I have doubtless made a newbie error! 😉

Flow below:

Screenshot 2021-09-23 154743.png

Thanks,

Tom

Categories:

Building flows

I have the same question (0)

All responses (2)

Answers (0)

Sort by

eric-cheng 5,171 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @billicatons ,

Based on your flow and the fact there are no other SharePoint actions, it shouldnt be the case.

If you look at the flow run history and the trigger output, is the ID correct?

In your list, have you verified the list item ID of the item that was edited is in fact different to the one in the flow? You will only get a new ID if a new item is created.

--------------------------------------------------------------------------
If I have answered your question, please mark my post as a solution
If you have found my response helpful, please give it a thumbs up

Connect on LinkedIn

Was this reply helpful? Yes No
billicatons 3 on at

Like
a
(0)

Report
Copy link

Link copied!

Thank you, @eric-cheng ! I think I found the issue when looking at the outputs as you suggested. I had missed that the ID of a list item in Sharepoint did not match the Title of the item (which also contained an ID number, 1 different from the actual item ID). So that was the source of the mismatch.

Thanks for your help.

Was this reply helpful? Yes No