Values.MergeProfilesRequestSourceRuns an AWS Lambda job that does the following: All the profileKeys in the ProfileToBeMerged will be moved to the main profile. All the objects in the ProfileToBeMerged will be moved to the main profile. All the ProfileToBeMerged will be deleted at the end. All the profileKeys in the ProfileIdsToBeMerged will be moved to the main profile. Standard fields are merged as follows: Fields are always "union"-ed if there are no conflicts in standard fields or attributeKeys. When there are conflicting fields: If no SourceProfileIds entry is specified, the main Profile value is always taken. If a SourceProfileIds entry is specified, the specified profileId is always taken, even if it is a NULL value. You can use MergeProfiles together with GetMatches, which returns potentially matching profiles, or use it with the results of another matching system. After profiles have been merged, they cannot be separated (unmerged).
type nonrec t = {domainName : Name.t;The unique name of the domain.
*)mainProfileId : Uuid.t;The identifier of the profile to be taken.
*)profileIdsToBeMerged : ProfileIdToBeMergedList.t;The identifier of the profile to be merged into MainProfileId.
*)fieldSourceProfileIds : FieldSourceProfileIds.t option;The identifiers of the fields in the profile that has the information you want to apply to the merge. For example, say you want to merge EmailAddress from Profile1 into MainProfile. This would be the identifier of the EmailAddress field in Profile1.
*)}val make :
?fieldSourceProfileIds:??? ->
domainName:Name.t ->
mainProfileId:Uuid.t ->
profileIdsToBeMerged:ProfileIdToBeMergedList.t ->
unit ->
t