amazonka-customer-profiles-2.0: Amazon Connect Customer Profiles SDK.
Copyright(c) 2013-2023 Brendan Hay
LicenseMozilla Public License, v. 2.0.
MaintainerBrendan Hay
Stabilityauto-generated
Portabilitynon-portable (GHC extensions)
Safe HaskellSafe-Inferred
LanguageHaskell2010

Amazonka.CustomerProfiles.Types.ConflictResolution

Description

 
Synopsis

Documentation

data ConflictResolution Source #

How the auto-merging process should resolve conflicts between different profiles.

See: newConflictResolution smart constructor.

Constructors

ConflictResolution' 

Fields

  • sourceName :: Maybe Text

    The ObjectType name that is used to resolve profile merging conflicts when choosing SOURCE as the ConflictResolvingModel.

  • conflictResolvingModel :: ConflictResolvingModel

    How the auto-merging process should resolve conflicts between different profiles.

    • RECENCY: Uses the data that was most recently updated.
    • SOURCE: Uses the data from a specific source. For example, if a company has been aquired or two departments have merged, data from the specified source is used. If two duplicate profiles are from the same source, then RECENCY is used again.

Instances

Instances details
FromJSON ConflictResolution Source # 
Instance details

Defined in Amazonka.CustomerProfiles.Types.ConflictResolution

ToJSON ConflictResolution Source # 
Instance details

Defined in Amazonka.CustomerProfiles.Types.ConflictResolution

Generic ConflictResolution Source # 
Instance details

Defined in Amazonka.CustomerProfiles.Types.ConflictResolution

Associated Types

type Rep ConflictResolution :: Type -> Type #

Read ConflictResolution Source # 
Instance details

Defined in Amazonka.CustomerProfiles.Types.ConflictResolution

Show ConflictResolution Source # 
Instance details

Defined in Amazonka.CustomerProfiles.Types.ConflictResolution

NFData ConflictResolution Source # 
Instance details

Defined in Amazonka.CustomerProfiles.Types.ConflictResolution

Methods

rnf :: ConflictResolution -> () #

Eq ConflictResolution Source # 
Instance details

Defined in Amazonka.CustomerProfiles.Types.ConflictResolution

Hashable ConflictResolution Source # 
Instance details

Defined in Amazonka.CustomerProfiles.Types.ConflictResolution

type Rep ConflictResolution Source # 
Instance details

Defined in Amazonka.CustomerProfiles.Types.ConflictResolution

type Rep ConflictResolution = D1 ('MetaData "ConflictResolution" "Amazonka.CustomerProfiles.Types.ConflictResolution" "amazonka-customer-profiles-2.0-7iC4NjyJEW8JuQGNtDiJ1f" 'False) (C1 ('MetaCons "ConflictResolution'" 'PrefixI 'True) (S1 ('MetaSel ('Just "sourceName") 'NoSourceUnpackedness 'NoSourceStrictness 'DecidedStrict) (Rec0 (Maybe Text)) :*: S1 ('MetaSel ('Just "conflictResolvingModel") 'NoSourceUnpackedness 'NoSourceStrictness 'DecidedStrict) (Rec0 ConflictResolvingModel)))

newConflictResolution Source #

Create a value of ConflictResolution with all optional fields omitted.

Use generic-lens or optics to modify other optional fields.

The following record fields are available, with the corresponding lenses provided for backwards compatibility:

$sel:sourceName:ConflictResolution', conflictResolution_sourceName - The ObjectType name that is used to resolve profile merging conflicts when choosing SOURCE as the ConflictResolvingModel.

$sel:conflictResolvingModel:ConflictResolution', conflictResolution_conflictResolvingModel - How the auto-merging process should resolve conflicts between different profiles.

  • RECENCY: Uses the data that was most recently updated.
  • SOURCE: Uses the data from a specific source. For example, if a company has been aquired or two departments have merged, data from the specified source is used. If two duplicate profiles are from the same source, then RECENCY is used again.

conflictResolution_sourceName :: Lens' ConflictResolution (Maybe Text) Source #

The ObjectType name that is used to resolve profile merging conflicts when choosing SOURCE as the ConflictResolvingModel.

conflictResolution_conflictResolvingModel :: Lens' ConflictResolution ConflictResolvingModel Source #

How the auto-merging process should resolve conflicts between different profiles.

  • RECENCY: Uses the data that was most recently updated.
  • SOURCE: Uses the data from a specific source. For example, if a company has been aquired or two departments have merged, data from the specified source is used. If two duplicate profiles are from the same source, then RECENCY is used again.