Dynamics Community Forum Thread Details

Unable to Create a copy of Segment

Hello Community,

Some context:

We have a Power Automate to automatically create Segments (msdynmkt_segmentdefinition then msdynmkt_segment) triggered at the update of

a custom entity. This Power Automate uses a Service Principal to connect to the Dataverse. Owners and Source Segment Created by are the users who updated the custom entity record that triggered the PA. The Created by is the Service Principal and the Modified By is Microsoft service account D365 Native Segments #

When I try to Create a copy (ribbon button) of the Segment I receive such error:

User does not have required privileges. Exception details: Identity user identityUser.SystemUserId=d37188ff-73ed-ec11-bb3d-000d3adc5baf, identityUser.Privileges.Count=1790, identityUser.Roles.Count=4 is missing prvOverrideCreatedOnCreatedBy privilege (Id=d48cf22f-f8c2-4e16-89eb-49f8281de4ea) on OTC=0 for entity '' (LocalizedName=''). Consider adding missed privilege to one of the principal (user/team) roles.

SystemUser d37188ff-73ed-ec11-bb3d-000d3adc5baf being D365 Native Segments #

I also encountered the issue of not having the option to Refresh segment on Segments created by this PA.

I don't have this issue on Segments created in the UI, I can Refresh segment and Create a copy, even though these Segments are also modified by D365 Native Segments #.

Requirement: I do not want to give D365 Native Segments # the miscellaneous privilege prvOverrideCreatedOnCreatedBy!

Categories:

Dynamics 365 Customer Insights - Journeys

1: Create Segments via Custom API (Under Impersonated User Context)
Instead of creating segments using the Service Principal directly:

Use HTTP call (Dataverse Web API) or custom connector in Power Automate
Set "Caller" (impersonated user) to the user who modified the triggering record

This ensures "Created By" and "Owner" are the actual user, not the service principal, avoiding the internal impersonation issue.

2: Use Power Automate Action "Perform an unbound action" (SystemUser context)
Use Perform an unbound action with CreateSegment if available and impersonate a licensed user.
Option 3: Post-creation Patch to "CreatedBy" (Not supported)
Not officially supported, but some teams use direct API manipulation to patch createdby on the segment — this is risky and unsupported.

Quick Links