We cried uncle and are temporarily abandoning the effort to move our attachments to sharepoint or file server doc types (until after our upgrade to 2025.2). I installed the Edge Agent, and tested opening a classic form successfully. It’ll also open local .pdf files successfully.
Unfortunately, opening .lnk file attachments via an Edge Agent classic form are confusing windows, and it can’t find an associated program to open it with. Weird, since I can open it in file explorer or with the classic program in the client just fine.
Long shot…but can you set up a Document Association for the lnk extension and specify Explorer there? Not sure if Edge Agent uses this, and we don’t use it with the client, but the documentation makes it sound like it’s what you want.
That is probably because smart client was .NET Framework and EA is .NET Core app, sometimes they work differently. Not sure what is the exact reason though.
Sometimes people copy and email and attach shortcut links by accident. It happens. Usually to someone a few days after they say why would anyone do that, because that’s how the universe is sometimes.
Taking a step back, if you open classic up (the normal way not through the edge agent) does the .lnk work that way?
The other thing I have experienced is .msg files won’t open directly through the browser even if you setup the file types etc. When I logged a ticket, the reposnse was you are SOL sorry
@Mark_Wonsil From Outlook. By default dragging and dropping as an saves the email as a .msg, just as it does in Classic, it’s the opening where you only get the option to view in ECM or download
