Moving from Classic to Kinetic.
In Classic I had a function that created an Outlook email. The classic customized screen code populated it and opened it on the users screen for a final check before sending.
Since, in Kinetic, all functions and code now run on the server that’s become problematic. My Initial thought was to copy Microsoft.Office.Interop.Outlook.dll to the server and create the email there. But it can’t even get based the first line of code before crashing.
Microsoft.Office.Interop.Outlook.Application App = new Microsoft.Office.Interop.Outlook.Application();
I’ve copied over the .dll and set my reference and using.
It just crashes right here.
A REAL coding area with better inline assistance and a good method of doing line by line debugging would really help. I feel that toolset is not really at ‘release ready’
Is Office installed on the server hosting this? Assuming it’s a server within your control.
It likely never will given how little attention tools gets. An idea can be submitted on specific asks and I bet many in this community would be incentivized to vote for those changes.
That was my thought to. I’m trying the install now. A LOT of my Classic customizations rely on this type of local client access. It’s annoying and there are insufficient tools to fix it well.
I might have to. Some kind of HTML display to show the formatted email before sending but extra step to redo what I had before in a simpler manner.
I love functions for doing things with data on the server but the client side is more difficult.
If so, you can make a REST call from the server to create a draft. Nothing to install and it will work with users who are not on Windows (iOS, Android, Mac).
Both Chat-GPT and Claude came up with plausible solutions for creating a .eml file with just native .net framework libraries, which if downloaded should open in outlook.
I think @Mark_Wonsil solution is the cleanest as long as you use M365
I get what you are saying. We use Role Based Access Control for Applications in Exchange Online to at least scope the application’s api permissions down to the groups that actually need access (in our case 4 people in 1 role). I’d love to hear if someone knows of a better way.