A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
I have resolved my own problem with a bit of a workaround.
To date, the programmatically Encoded Absolute URL generated by SPD and used in a notification email which is part of an SPD workflow no longer opens the file in Office Online anymore as it did less than a month ago. However, by adding ?web=1to the end of the encoded URL, it works perfectly. So, here's an illustration:
In SPD
In the email as I created it using SPD,
- Using just the Encoded Absolute URL option it looks like this:
[%Current Item:Encoded Absolute URL%]
- Adding the extra code to it, it looks like this
[%Current Item:Encoded Absolute URL%]?web=1
In Outlook
Then, what's the result in the actual email generated by the workflow and received in your Outlook inbox?
- Using only the Encoded Absolute URL, the URL is
https://tenantname.sharepoint.com/sites/sitename/libraryname/Test%20Spreadsheet%202.xlsx
But that will only open the file in the full functional Office application (in this case Excel) no matter what settings I set for the library regarding opening in a browser or not.
- But with the addition of ?web=1 at the end, the URL is
https://tenantname.sharepoint.com/sites/sitename/libraryname/Test%20Spreadsheet%202.xlsx?web=1
And that makes it open in the browser for the Office application (Read only).
It's not a fix; not sure why the Encoded Absolute URL provided by SPD no longer works, but it solved my problem so I could deliver the workflow to my customers.