Create a person relationship
post
/fscmRestApi/resources/11.13.18.05/hedPersonRelationships
Request
Header Parameters
-
Metadata-Context: string
If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
-
REST-Framework-Version: string
The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
-
Upsert-Mode: string
Contains one of the following values: true or false. If true, the server performs an Upsert operation instead of a Create operation. During an Upsert operation, the server attempts to find an existing resource that matches the payload. If a match is found, the server updates the existing resource instead of creating a new one. If not found or false (default), the server performs a Create operation. Note that the Upsert operation isn't supported for date-effective REST resources.
Supported Media Types
- application/json
Root Schema : schema
Type:
Show Source
object
-
ObjectPersonPartyId: integer
(int64)
Title:
Object Person Party ID
The object person party ID. -
RelationshipCode: string
Title:
Relationship Code
Maximum Length:30
The code of the relationship. -
RelationshipTypeCode: string
Title:
Relationship Type
Maximum Length:30
The person relationship type code. A list of accepted values is defined in the lookup type HZ_RELATIONSHIP_TYPE. -
SubjectPersonPartyId: integer
(int64)
Title:
Subject Person Party ID
The subject person party ID.
Response
Supported Media Types
- application/json
Default Response
The following table describes the default response for this task.
Headers
-
Metadata-Context:
If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
-
REST-Framework-Version:
The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Root Schema : hedPersonRelationships-item-response
Type:
Show Source
object
-
EndDate: string
(date)
Title:
To Date
Read Only:true
The end date of the relationship. -
links: array
Links
Title:
Links
The link relations associated with the resource instance. -
ObjectPersonEmailAddress: string
Title:
Email
Read Only:true
Maximum Length:320
The object person email address. -
ObjectPersonFirstName: string
Title:
First Name
Read Only:true
Maximum Length:150
The object person first name. -
ObjectPersonFullName: string
Title:
Full Name
Read Only:true
Maximum Length:360
The object person full name. -
ObjectPersonLastName: string
Title:
Last Name
Read Only:true
Maximum Length:150
The object person last name. -
ObjectPersonMiddleName: string
Title:
Middle Name
Read Only:true
Maximum Length:60
The object person middle name. -
ObjectPersonPartyId: integer
(int64)
Title:
Object Person Party ID
The object person party ID. -
RelationshipCode: string
Title:
Relationship Code
Maximum Length:30
The code of the relationship. -
RelationshipId: integer
(int64)
Title:
Relationship ID
Read Only:true
The relationship ID. -
RelationshipMeaning: string
Title:
Relationship Meaning
Read Only:true
Maximum Length:80
The meaning of the relationship. A list of accepted values is defined in the lookup type PARTY_RELATIONS_TYPE. -
RelationshipTypeCode: string
Title:
Relationship Type
Maximum Length:30
The person relationship type code. A list of accepted values is defined in the lookup type HZ_RELATIONSHIP_TYPE. -
RelationshipTypeMeaning: string
Title:
Relationship Type Meaning
Read Only:true
Maximum Length:80
The meaning of the relationship type. A list of accepted values is defined in the lookup type HZ_RELATIONSHIP_TYPE. -
StartDate: string
(date)
Title:
From Date
Read Only:true
The start date of the relationship. -
SubjectPersonEmailAddress: string
Title:
Email
Read Only:true
Maximum Length:320
The subject person email address. -
SubjectPersonFirstName: string
Title:
First Name
Read Only:true
Maximum Length:150
The subject person first name. -
SubjectPersonFullName: string
Title:
Full Name
Read Only:true
Maximum Length:360
The subject person full name. -
SubjectPersonLastName: string
Title:
Last Name
Read Only:true
Maximum Length:150
The subject person last name. -
SubjectPersonMiddleName: string
Title:
Middle Name
Read Only:true
Maximum Length:60
The subject person middle name. -
SubjectPersonPartyId: integer
(int64)
Title:
Subject Person Party ID
The subject person party ID.
Nested Schema : Links
Type:
array
Title:
Links
The link relations associated with the resource instance.
Show Source
Nested Schema : link
Type:
Show Source
object
-
href: string
Title:
hyperlink reference
The URI to the related resource. -
kind: string
Title:
kind
Allowed Values:[ "collection", "item", "describe", "other" ]
The kind of the related resource. -
name: string
Title:
name
The name of the link to the related resource. -
properties: object
properties
-
rel: string
Title:
relation
Allowed Values:[ "self", "lov", "parent", "canonical", "child", "enclosure", "action", "custom" ]
The name of the relation to the resource instance. Example: self.
Nested Schema : properties
Type:
Show Source
object
-
changeIndicator: string
Change indicator or the ETag value of the resource instance.
Links
- hedRelationshipTypesLOV
-
Parameters:
- finder:
PersonRelationshipTypeFinder%3BInUseRelationshipCode%3D{RelationshipCode}%2CInUseRelationshipTypeCode%3D{RelationshipTypeCode}
The following properties are defined on the LOV link relation:- Source Attribute: RelationshipCode; Target Attribute: RelationshipCode
- Display Attribute: RelationshipMeaning
- finder: