Welcome to the Sage 200 Evolution ideas Portal
No Local COM Object (Outlook.Application) Classic Outlook had a COM object (Outlook.Application) that allowed external programs (e.g., VBA, PowerShell, or C#) to create and manipulate Outlook instances programmatically. The new Outlook is based on a web-based architecture and does not expose this COM object, making traditional automation methods break. Describe why this enhancement is needed: Incase microsoft move from Classic Outlook had a COM object (Outlook.Application) that allowed external programs (e.g., VBA, PowerShell, or C#) to create and manipulate Outlook instances programmatically to new Outlook that is based on a web-based architecture which does not expose this COM object, making traditional automation methods break.
What is the workaround for the problem today?
Use the normal outlook/smtp feature that is current availablr |
|
Your Designation/Role | Other |
Email. |