Create publication maps

post

/fscmRestApi/resources/11.13.18.05/publicationMaps

Request

Header Parameters
  • 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".
  • 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.
  • 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
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
Nested Schema : Publication Map Translations
Type: array
Title: Publication Map Translations
A publication map translation lets you translate the publication map name and publication map description to a specified language.
Show Source
Nested Schema : Spoke Attributes
Type: array
Title: Spoke Attributes
A spoke system represents spoke system columns in a publication map. Spoke system columns that are mapped with master data columns appear in the publication output.
Show Source
Nested Schema : schema
Type: object
Show Source
Nested Schema : publicationMaps-spokeColumns-item-post-request
Type: object
Show Source
Nested Schema : Master Attributes
Type: array
Title: Master Attributes
Master data columns mapped with spoke system columns in a publication map. A master data column can be mapped with multiple spoke system columns.
Show Source
Nested Schema : publicationMaps-spokeColumns-masterDataColumns-item-post-request
Type: object
Show Source
Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • 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".
  • 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.
Body ()
Root Schema : publicationMaps-item-response
Type: object
Show Source
Nested Schema : Publication Map Translations
Type: array
Title: Publication Map Translations
A publication map translation lets you translate the publication map name and publication map description to a specified language.
Show Source
Nested Schema : Spoke Attributes
Type: array
Title: Spoke Attributes
A spoke system represents spoke system columns in a publication map. Spoke system columns that are mapped with master data columns appear in the publication output.
Show Source
Nested Schema : publicationMaps-publicationMapTranslations-item-response
Type: object
Show Source
Nested Schema : publicationMaps-spokeColumns-item-response
Type: object
Show Source
Nested Schema : Master Attributes
Type: array
Title: Master Attributes
Master data columns mapped with spoke system columns in a publication map. A master data column can be mapped with multiple spoke system columns.
Show Source
Nested Schema : publicationMaps-spokeColumns-masterDataColumns-item-response
Type: object
Show Source
Back to Top