Answered

Does Dataverse treat email 'Message ID' as case-sensitive?

(0) Share

Report

Posted on by asolvak

Hi,
I have a flow that uses Get Email V3 action to import emails into Dataverse 'Email Messages' table. I use it for storing important emails from (or to) the suppliers.
I experience issues when I get two message ID's that appear similar except 1 character that is lowercase rather than uppercase. They are considered identical by Dataverse. Which leads to a question about case-sensitivity when handling message ID's.
I've also had issues when importing messages with ID's that differ by several characters among the last 10 characters of the ID - they have also been considered identical by Dataverse. Which leads to a question that is there a string length limitation when comparing strings?

The emails causing issues are from various periods in the past and sent from various different mailboxes and I still get lots of errors. The senders/receivers are different, but ID's are treated as identical.

I have created a special Inbox subfolder in my current mailbox for importing older emails where I place the copies from older .pst files. Could this be the cause of it?

I would appreciate any ideas how to solve this issue.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (2)

Answers (1)

asolvak 6 on at

Like (0)

Report
Copy link

Link copied!

I have conducted further test and want to add following:
1) Condition action in Power Automate doesn't distinguish email message ID's ending with "...uAAA=" and "UAAA=" from each-other (this is common knowledge already)
2) When I redirect the flow to bypass the condition block (go straight to adding a row), then I get an error from dataverse Add row action: "Cannot insert duplicate key row in object 'dbo.ActivityPointerBase' with unique index 'fndx_Email_MessageId'. The duplicate key value is <redacted>." I get a list of different API keys, but Message ID is not among them.

3) At the same time the filtering of Message ID column in Dataverse Email table on above Message ID values shows that this column is case-sensitive and doesn't consider the those IDs to be identical.

Thus it seems the fault lies somewhere in the email import and row adding process (into 'dbo.ActivityPointerBase'). Can anybody suggest how to overcome this?

1 people found this reply helpful.

Was this reply helpful? Yes No
Verified answer

stampcoin 5,146 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

@asolvak Hi,

I assume that you already managed activityid.

When manipulate message ID, please use internetMessageId instead of using ID (the one you got from Get Email v3), you will see it when you check the output from Get Email V3.

Below is from eventMessageResponse resource type

id, the Unique identifier for the message. By default, this value changes when the item is moved from one container (such as a folder or calendar) to another. To change this behavior, use the Prefer: IdType="ImmutableId" header. See Get immutable identifiers for Outlook resources for more information. Read-only.

It's better to use internetMessageId for MessageID column, ( keep angle brackets when save it in the column).

try that.

1 people found this reply helpful.

Was this reply helpful? Yes No