# MappingSpecificationType (Complex Type)

### Namespace: http://midpoint.evolveum.com/xml/ns/public/common/common-3

See Axiom.

Item Summary
Name | Type | Multiplicity | Description
--- | --- | --- | ---
assignmentId | property string | [0,1] |
definitionObjectRef | reference ObjectReferenceType | [0,1] | Object in which the mapping resides.
objectType | container ResourceObjectTypeIdentificationType | [0,1] | Object type (like account/default) in which this mapping is defined.
mappingName | property string | [0,1] |

- ### Items

  - #### assignmentId

    Flags: RAM,runtime

    Multiplicity: [0,1]

  - #### definitionObjectRef

    Flags: RAM

    Multiplicity: [0,1]

    Object in which the mapping resides. Beware: when the mapping is related to a resource that uses a resource template, i.e., that has a super-resource, the actual (expanded, child) resource OID is provided here, even if the mapping physically resides in the super-resource.

  - #### objectType

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Object type (like account/default) in which this mapping is defined. This is necessary to avoid requiring mapping name uniqueness across the whole resource, but also to ensure working of mappings (1) inherited from the super-type to subtypes, (2) applied to multiple object types (like those in association types). Such mappings would have the same specification even when they are in fact executed as two distinct instances on different data. Currently provided for inbound mappings.

  - #### mappingName

    Flags: RAM,runtime

    Multiplicity: [0,1]