Unanswered

Flow email troubles

(0) Share

Report

Posted on by Community Power Pla...

Hello,

I have an issue.

I have been using flows send emails to users. In the email would be a hyperlink to the application with a query string on the link. These links have suddenly begun to have different behavior. I would use the value on the query string to LookUp a record in a SharePoint list.

Expected behavior that has been working until recently was that after clicking the link the application would open up to the correct screen and display the correct item based on ID. Instead, now when I click the link the application opens up to the oldest record (The lowest number ID) and does not use the query string or discards it. Let's look at some code to get a better feel of what I'm trying to say.

A flow generates the above link and emails a user. The user clicks the link. The ?ID={Dynamic ID} is making use of flow dynamic properties. The ID relates to the automatically generated SharePoint ID for every record.

When the user navigates to the application -- the screen BrowseScreen1 has this code on the property "OnStart".

If(IsBlank(Param("ID")),
Navigate(BrowseGallery1, ScreenTransition.Fade)
,Navigate(DetailScreen1, Cover,
{device:LookUp(ECTCR_Tracking, ID = Value(Param("ID")))}))

That code has been working all day. Then suddenly after lunch, it has stopped. I have not messed with the code in between. So I would just like a little help understanding what is happening.

Thanks for the help.

Categories:

Using flows

I have the same question (0)

All responses (3)

Answers (1)

v-xida-msft on at

Like (0)

Report

Hi @Johnathon_S,

Could you please share a screenshot of your flow’s configuration?
Could you show a bit more about the data type of Dynamic ID?

Further, please check if the Dynamic ID has been passed to PowerApps app?

Note:
You can upload a pbix file to Onedrive or any web storage and share the link. Do mask sensitive data before uploading.

Best regards,

Kris

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report
If(IsBlank(Param("ItemID")), Navigate(BrowseGallery1, ScreenTransition.Fade) ,Navigate(DetailScreen1, Cover, {device:LookUp(ECTCR_Tracking, ID = Value(Param("ItemID")))}))
(Changed ID to ItemID in case that might be confusing PowerApps)

Was this reply helpful? Yes No
Verified answer

Community Power Pla... on at

Like (0)

Report
Alright,

for whatever reason when the OnStart function runs it was navigating correctly but not able to bring the correct ID. No idea what it grabbed the lowest ID number to use that.

To fix this I had to change the OnStart function to check if the param was empty, if it was empty then stay on the browsegallery1 screen. If it was not empty, navigate to the DetailForm1 screen.

If(IsBlank(Param("ItemID")),
ResetForm(EditForm1);
NewForm(EditForm1);
Navigate(EditScreen1, ScreenTransition.Fade),
Navigate(DetailForm1, Cover))

On the FormDetails1 screen, I selected the Item property and did the LookUp with the param there. However, to keep everything working correctly I needed an If() to check if the query string was blank again. If it is, when navigating to the detail screen don't use the LookUp() and instead, display the details of the selected browsergallery1 item.

If(IsBlank(Param("ItemID")), BrowseGallery1.Selected, LookUp(ECTCR_Tracking, ID = Value(Param("ItemID"))))

This seems to be a solution I can live with. I don't know why my original source code stopped working correctly.

Was this reply helpful? Yes No