SPUserProfileProperty: Allow several mapping connections

Details of the scenario you try and problem that is occurring: Currently we are working with a customer that uses several mapping connections for one User Profile Property.

With the current resource, there is no support to set several mapping connections for one property.

Adding this capability would result in a breaking change. We would have to add a new custom type to make the resource more versatile. I can think of a addition like this:

Current state of resource:

SPUserProfileProperty WorkEmailProperty
{
    Name = "WorkEmail2"
    Ensure = "Present"
    UserProfileService = "User Profile Service Application"
    DisplayName = "Work Email"
    Type = "Email"
    Description = "" #implementation isn't using it yet
    PolicySetting = "Mandatory"
    PrivacySetting = "Public"
    MappingConnectionName = "contoso.com"
    MappingPropertyName = "mail"
    MappingDirection = "Import"
    Length = 10
    DisplayOrder =25 
    IsEventLog =$false
    IsVisibleOnEditor=$true
    IsVisibleOnViewer = $true
    IsUserEditable = $true
    IsAlias = $false 
    IsSearchable = $false 
    TermStore = ""
    TermGroup = ""
    TermSet = "" 
    UserOverridePrivacy = $false
    PsDscRunAsCredential = $SetupAccount
}

Proposed change:

SPUserProfileProperty WorkEmailProperty
{
    Name                 = "WorkEmail2"
    Ensure               = "Present"
    UserProfileService   = "User Profile Service Application"
    DisplayName          = "Work Email"
    Type                 = "Email"
    Description          = "" #implementation isn't using it yet
    PolicySetting        = "Mandatory"
    PrivacySetting       = "Public"
    Mapping              = @(
        MSFT_SPUserProfilePropertyMapping {
            ConnectionName = "contoso.com"
            PropertyName   = "mail"
            Direction      = "Import"
        }
    )
    Length               = 10
    DisplayOrder =25 
    IsEventLog =$false
    IsVisibleOnEditor=$true
    IsVisibleOnViewer    = $true
    IsUserEditable       = $true
    IsAlias              = $false 
    IsSearchable         = $false 
    TermStore            = ""
    TermGroup            = ""
    TermSet              = "" 
    UserOverridePrivacy  = $false
    PsDscRunAsCredential = $SetupAccount
}

[ykuijs]

Hi @andikrueger I lost track of this issue, my apologies. I agree with you that we should extend this resource. If a mapping exists in SharePoint, which is not in the MSFT_SPUserProfilePropertyMapping array, we should remove it. That way we make sure the exact array is configured in SharePoint.

[andikrueger]

I will push my changes to this branch. Currently I need to setup a new test environment with a minimum of two connections - doh!