Skip to main content

Posts

Featured

Why Email Activity Parties Still Resolve to Unexpected Records Even After Changing an Email Column to Text

We had a custom text column on the Queue table that stored a shared mailbox address for reference. At some point the column was set up with the Email format, and several queues had the same address in that column. Later we changed the column format from Email to Text, because it was only for reference and wasn't meant to take part in email processing. After that, incoming emails sent to that address kept resolving to all the queues that had the value in the custom column. They didn't resolve only to the queue whose primary email address matched. The format was no longer Email, but Dataverse was still matching the address to those queue records when it resolved the activity parties. TL;DR: Changing a column's format from Email to Text doesn't remove its existing values from the internal EmailSearch table, so use the DoNotResolve flag (or clear the values while the column is still Email-formatted) before you change the format. What is the EmailSearch Table? Dataverse k...

Latest posts

Click-to-Act Not Working in Customer Service Workspace Tabs with a Third-Party CTI Provider

Dataverse Table Metadata Not Updating During Managed Solution Import

Fixing the Dataverse MCP "Describe" Tool FileLoadException in Copilot Studio

Tracing Undocumented Application Users in Dataverse

Image

Power Automate Cloud Flow Failing with 403 Forbidden on a Dataverse Action

Quick Tip: Finding the Right Many-to-Many Relationship When Adding Subgrids

Image

Dataverse Connector's "Return Full Metadata" Parameter in Power Automate

Image

Troubleshooting Copilot Studio Autonomous Agent "Incomplete" Status

Image

PowerFx to Add Row Numbers to Data Tables Directly

Image

Fixing Date Decrement Issues in Dynamics 365 Project Operations Tasks Grid