Outlook Email returned with duplicate IDs

Question

Hi Team,

We are currently facing an issue where we are receiving emails with the same ID from the API. This is leading to missed captures through our request since there are two different emails received with identical IDs. The ID is crucial for us to distinguish between unique emails.

We kindly request your assistance in resolving this scenario to ensure the accurate capturing and storage of emails without any duplication. Your prompt attention to this matter is highly appreciated.

Example ID we receive in the API response highlighted in bold:

{

"@odata.etag": "W/"CQAAABYAAACSfMzaqyWjQalHSlfhEdKGAAUfklg9"",

"id": "AAMkAGRkNjc0NzUzLWUwZTgtNDYzYy04MmVjLTA3YjVlMzU1YjA0MgBGAAAAAACFjOkrM98TSoI-VaEXxqZLBwCSfMzaqyWjQalHSlfhEdKGAATa7CZmAACSfMzaqyWjQalHSlfhEdKGAAUgcrVtAAA=",

"receivedDateTime": "2024-02-22T01:43:11Z",

"subject": "ApexOne - Import & Export Branded Mobile Phones & Original Accessories",

"isRead": true,

"from": {

"emailAddress": {

"name": "MobileSources.Net",

"address": "*** Email address is removed for privacy ***"

}

}

},

Shivam

Answer 1

Hi!

This issue is still hot.

When loading mails from API all separate mails seem to be identified and processed correctly even when ID objects are handed over from one process to another.

Error occurs when mail ID and Outlook ID are written into text file or as a blob name. Seems like ID-s have non-printing characters, that are omitted in URL, file text or in visible file name.

Scenario: Workflow stores API response as a JSON file on Azure Blob Storage with MailID as file name. The file is discoverable with Power BI Azure Storage plugin and file content is loaded into Power BI, as Power BI does not care about unique values in file name list after all file contents have been received. Several records have duplicate ID contents and duplicate Outlook ID-s and only one of the records (JSON file) is discoverable in Azure Storage. The files that have malformed ID as file name are not visible through Storage Explorer, Azure GUI and ID/content are out of sync in PowerBI table.