OneDrive for Business connection references a document library GUID when transacted from AppSource?

(1) Share

Report

Posted on by EEasterday

I have noticed that customers transacting my Model Driven PowerApp from AppSource have experienced issues with the power automate flows that contain connectors to OneDrive for Business. The issue is that the "document library" section of the connection seems to be pointing to a GUID (possibly left over from my development of the application?). See the screenshot below for an example. I have been helping customers fix this manually, but that is obviously a clunky and less than ideal solution. Of note, the app contains many flows and connections, when they initially download the solution we turn on connections by going to the default solution and creating the connections. This doesn't seem to affect the OneDrive document library selection inside the flows.

Any suggestions?

Thanks for your help!

The section that is highlighted is the issue. Of course in my own environments it appears as below. In other organizations after install from AppSource, the "Document Library" has a long GUID. The solution has been to open the flow and delete the GUID, then use the dropdown to select OneDrive.

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Michael E. Gernaey 53,974 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi

1) You should never have to go create connections. They should be environment variables in your solution and in no way does that require using the connection tab to create them.

2) make sure you remove your value from the variable before you export so that they have to set it

3) you are also essentially breaking their environment. Never should you have someone change immutable things in a managed solution so that it creates unmanaged layers. It is going to cause them issues in the future

You should be testing your own import in another environment before it goes on app source to resolve these types of issues.

they are going to need to manually delete and cleanup your solution and unmanaged layers it’s creating.

Was this reply helpful? Yes No
EEasterday 52 on at

Like (0)

Report
Copy link

Link copied!

Thank you for your response!

It is my understanding that the actual connections to services still must be made, as there is a credential/authentication required to interact with the connector itself. To address your #3 concern, this is why we have chosen to have clients establish the service connections using the default solution since it does not then create a managed layer inside our managed app solution.

May I ask how you would use the environment variable to point to the document library above using the data types available (JSON, text, data source, etc.)?

Was this reply helpful? Yes No