Answered

Old Power Automate in IntelliSense even though not connected in app

(0) Share

Report

Posted on by ScottRMeredith

141

I have an app suite I built a few years ago for a unit at my work. A similar unit wanted the same app suite. I put the apps, and flows into a solution. Created a bunch of environment variables, and imported to a different environment. Then I made the modifications that were applicable to the new one, both apps and flows. I have one app that is refusing to use the IntelliSense reference of the new flow in the app. I have refreshed the flow. Removed and re-added the flow. Removed the flow, published, closed, re-opened, re-add the flow and it still only shows the old flow from the original app in IntelliSense. I cleared cache. I have edited the flow from within Power Apps, and just in Automate. I removed the environment variables, and put them back to just the sites and lists directly. How can I resolve this?

SEUAP is the old reference that isn't even in this environment. PEUAP are the new updated flows I am trying to use. When I try to type in a reference using the PEUAP prefix, it just underlines it as an error.

Categories:

Building Power Apps

I have the same question (0)

All responses (7)

Answers (1)

Sort by

WarrenBelz 155,352 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @ScottRMeredith,

One initial question here - were these flow originally created with those names, or have they been renamed at some point ? Try creating a new flow from the start (you should be able to do it in pieces with your Clipboard), remove the old one from the app and add the new one and see if that works.

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful?
Visit my blog Practical Power Apps LinkedIn

Was this reply helpful? Yes No
ScottRMeredith 141 on at

Like (0)

Report
Copy link

Link copied!

@WarrenBelz,

I had it in one environment originally. I put all the components of the app suite into a solution and imported it into a new environment for the new group. I then went in and re-named the flows and made the changes I needed. There are about 6 different apps in the solution, and this is the only one that is giving me a problem.

Was this reply helpful? Yes No
Verified answer

WarrenBelz 155,352 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @ScottRMeredith,

The reason I asked that is I have found on occasions, Power Apps "hangs on" to the original name of the Flow when referring to it in Intellisense and in valid syntax (I have a couple of those in apps at the moment), so I suspect what you are seeing is actually the Flows you are needing, so you might try and run them to see if they do as you expect.

I suggested testing this possibility by making a new flow and seeing if it was offered for connection.

Was this reply helpful? Yes No
ScottRMeredith 141 on at

Like (0)

Report
Copy link

Link copied!

Thanks for helping by the way @WarrenBelz, (I am not sure why the forum isn't letting me tag you)

I bring it up because this is what I got that originally brought my attention to it by a user. I noticed it was the SEUAP reference and went to my flow instances to see what the error may have been, but it didn't even make it out of Power Apps over to Automate, which made sense because I have error handling in all my flows that email me immediately if they fail, rather than wait for the weekly email.

Was this reply helpful? Yes No
WarrenBelz 155,352 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @ScottRMeredith,

So have you solved this with a workaround or is it still not doing what you need ?

Was this reply helpful? Yes No
ScottRMeredith 141 on at

Like (0)

Report
Copy link

Link copied!

@WarrenBelz,

That seemed to work. I create a new test flow with just a compose and respond back to power apps. It shows up correctly in IntelliSense. I added back in the flows I need. They still respond in IntelliSense with the wrong name, but now they run without throwing an error in the app, and no error from automate.

I don't have a user that can test it tonight, so once they test it in the morning, I will mark your response as the answer.

Thank you again.

Was this reply helpful? Yes No
WarrenBelz 155,352 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

HI @ScottRMeredith,

A quick follow-up to see if you received the answer you were looking for. Happy to assist further if not.

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful?
Visit my blog Practical Power Apps LinkedIn

Was this reply helpful? Yes No