Launching .docx from Power App crashes OneDrive

[cooneyr]

I have a template .docx that is populated in each DocSet created in SharePoint. The document contains a couple content controls (date pickers and check boxes). From my PowerApp app, I used the "ms-word:ofe|u|" and the document's link to successfully open the copied documents in the Word Desktop App, no problem there.

The issue is, after a short time, suddenly every copy of that template file freezes or even crashes OneDrive with a merge issue. The merge is repairable, but every time you open that Word document, it's gonna freeze/crash OneDrive again.

I found removing the "ms-word:ofe|u|"  from the launch was the fix (work around). You can open that same hanging-up Word document in the browser app, and then in the Desktop App from the browser app and everything works 100%. However, that extra step of opening the browser version to then open the Desktop App is not gonna fly.

Any thoughts on why the "ms-word:ofe|u|" is causing the document to hand up in OneDrive? Any other methods of opening the Word Desktop App? Thanks.

[v-xida-msft · Accepted solution]

Hi @cooneyr ,

Based on the issue that you mentioned, I have made a test on my side, and don't have the issue that you mentioned.

If you want to launch a word desktop from your canvas app, I think the following formula could achieve your needs:

Launch("ms-word:ofe|u|" & "Link to Doc")

I have made a test on my side, the screenshot as below:

I add a Gallery in my app, and connect it to my SP Library. Add a "Document" Icon in your Gallery, set the OnSelect property to following:

Launch("ms-word:ofe|u|" & First(Split(ThisItem.'Link to item',"?")).Result)

Note: I store many doc files in my SP Library the above Gallery connects to. In addition, please make sure the link you attached within the Launch function should be end with .doc or .docx. e.g. https://xxxxxx.sharepoint.com/sites/PowerApps/MyLibrary1/FY19%20Q1-Self-evaluation.docx

Best regards,

[cooneyr]

v-xida-msft

I accepted your solution, but I'm not 100% clear on if it was the fix or not. I connected to a new library and suddenly the issue wasn't occurring anymore. I tried to make it crash but it didn't. So then I also implemented your parsing function just as an additional step to keep this from happening again. Thank you for your help.