New Connector for Microsoft Office 365 - Outlook Released!

[ewilson]

All,

A new connector is available, on the Digital Exchange, for working with Microsoft Office 365 - Outlook. This is a complete design of the previous Microsoft Graph API - Outlook connector.

The new connector is implemented as a traditional VBO (Visual Business Object), so there are no issues with being able to download and save attachments directly from the connector. This connector has similar actions to the legacy Outlook VBO, but since it leverages Microsoft Graph API, behind the scenes, it does not require Outlook to be installed locally on the runtime resource.

Some things to be aware of:

• The legacy Outlook VBO exposed multiple actions (i.e. Basic, Advanced, and Expert) for retrieving emails from the Inbox or Sent Items folders. The new VBO simplifies and consolidates these multiple actions into a single action that support OData $search and $filter options. Refer to the documentation for links to further Microsoft information about using these properties.
• Microsoft limits the size of attachments when sending emails via the Graph API. Their documentation is a little confusing on what the actual max size is. The Graph API documentation implies that singular file attachments can be up to 150MB each, but Exchange Online limits the overall size of a Message (i.e. headers, body, attachments, etc all together) to no more that 150MB. In our testing, the latter appears to be the actual case. 

You can find the new connector at the following link:

Microsoft Office 365 - Outlook

#BPTechTips #DigitalExchange #Outlook

Cheers,
 ​​​

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------

[kiranb25]

@ewilson  I have gone through that post and validated the code by removing the reference of refence attachment and tried with output Json, still got the same error.

Any work around code for this issue for time being..?

Thanks,

[kiranb25]

@ewilson my bad, its working now.

Appreciate your quick response. thanks 

[ewilson]

@kiranb25 version 1.5.1 of the VBO was just posted to the DX. It addresses the attachment issue.

Cheers,
Eric

[Christer_Tellefsen]

Hi Eric,

I have an issue with Attachment File Paths in "Reply to Mail"

I recently connected to Microsoft Office 365 and have been testing the "Reply to Mail" and "Forward" feature. I encountered an issue when replying to an email with an attachment — the full file path is included in the attachment name instead of just the file name. For example, an attachment appears as C:\Users\%username\test.pdf instead of simply test.pdf.

Image :

I was wondering if this is something you are considering fixing in a future release. In the meantime, I am working to implement a solution by creating an extension of the code outside the official object to ensure only the file name is used.

Looking forward to your response.

Best regards,
Christer

[ewilson]

Hello @Christer_Tellefsen,

You're referring to when you pass attachments into the action, the full path of the individual files is included as the file name, correct?

Cheers,
Eric

[ewilson]

@Christer_Tellefsen 

Version 1.5.3 of the VBO has been published to the DX.

Cheers,
Eric

[Christer_Tellefsen]

Hi again,

We are increasingly using Graph API, but we've encountered a new issue related to attachments. When attempting to download an attachment that exceeds 5MB, we receive the following error:

"Could not execute code stage because exception thrown by code stage: Column '@odata.mediaContentType' does not belong to table."

Based on my research, I understand that Graph API should provide an @odata.nextLink for large attachments, but we are not receiving it in this case. Could you provide guidance on how to handle this situation, or suggest any adjustments we should make to properly retrieve large attachments?

Thank you for your assistance.

Best regards,
Christer Tellefsen

[ewilson]

@Christer_Tellefsen 

Which specific action are you using?

Cheers,
Eric

[Christer_Tellefsen]

We are using the "Get Attachments" feature.

I tested it today, and it's working for 5MB attachments. However, when handling larger attachments, we often encounter the following error:
System.OutOfMemoryException.

regards
Christer

[ewilson]

@Christer_Tellefsen what version of Blue Prism are you using? This error is seen in various cases when using 32-bit BP. 

Cheers,
Eric