Umanaged solution import seems to work, but flows are turned off bc SharePoint connections fail

(0) Share

Report

Posted on by dancostello

Hi all,

I've made a medium-sized solution (1 canvas app, a few flows, a couple dozen environment variables, etc.) that uses SharePoint as its primary data store.

- All flows and apps reference the SharePoint site, lists, and libraries via environment variables.

- I can easily export and import, managed or unmanaged, between environments in my tenant (using my dev SharePoint site for all of them).

When my client deploys it unmanaged into their tenant, it seems to work but many of the flows are turned off, and when we check them, many of the SharePoint actions say they're failing because of the connection to the SharePoint site.

- The connection references seem fine

- Some parts of the flows and the app connect to SharePoint fine

While troubleshooting, I had the client "Change Connection" on the broken steps, then create a new connection. This seemed to work, but then it failed again. I had him switch it *back* to the original connection and... it worked again.

This was for one of the smaller flows, it took a long time, and I don't know why it happened in the first place. I really don't want to have this guy grind through manually switching the connections on the like 3-dozen-plus SharePoint actions in the "big" flow, especially when I don't know why this happened in the first place or if it will work.

Has anyone seen anything like this before? Any suggestions?

Thank you!

Dan

All responses (2)

Answers (0)

dancostello 2 on at

Like (1)

Report

Umanaged solution import seems to work, but flows are turned off bc SharePoint connections fail

Hi @Michael E. Gernaey,

Thanks so much for the response.

- My environment variables do indeed have default values, but I did make a point of reviewing all of the values with the client to verify that they were correct. A couple of them were wrong, but fixing them didn't resolve the problem.

- Sorry for being unclear -- when, in the course of troubleshooting, I had the client abandon the environment-variable-defined connection reference and create a brand new SharePoint connection, it worked. And then it stopped working when we saved. And then I had him switch it back to the connection reference that was included in the solution in the first place, and then it worked.

- I very much appreciate the suggestion about pulling out the solution, deleting and re-creating the connections, then re-installing. I'm thinking I'll have them do that in a new environment tomorrow.

Fingers crossed -- I'll let you know if it solves the problem.

Thanks again!

Dan
Suggested answer

Michael E. Gernaey 38,519 Super User 2025 Season 1 on at

Like (0)

Report

Umanaged solution import seems to work, but flows are turned off bc SharePoint connections fail

Hi @dancostello

You said you are using Environment Variables.

can you please have them go look at the values that are there, after they import, because by default it would point to yours.

Have they been updated? as this is unmanaged its different than managed installation(a little bit). So make sure you are deleting the default setting before exporting it so it forces them to leverage new connections.

If they are, then I would have to see their environment to understand. But you said if they create a new one it breaks again. Breaks when? when they install a new version of the Solution? sounds like, Env variables and connection references aligned to them to me.

If this solves your problem please Mark as such and maybe a like :-)

If you have more questions please share. If you can get pictures that would help a lot. And if you can verify with them that at install are they creating or linking to new or existing connections?

I would also suggest if so, they delete all connections, NOT from the solution. Remove the solution totally. Make sure they are gone from the Connections Tab, then re-install. If that doesn't fix it, well you are cursed