Get a single preferred merchant list record
get
/fscmRestApi/resources/11.13.18.05/expenseTypes/{ExpenseTypeId}/child/preferredMerchantLists/{preferredMerchantListsUniqID}
Request
Path Parameters
-
ExpenseTypeId(required): integer(int64)
Value that uniquely identifies an expense type in an expense template.
-
preferredMerchantListsUniqID(required): string
This is the hash key of the attributes which make up the composite key--- ExpenseTypeId, MerchantListType and StartDate ---for the Preferred Merchant Lists resource and used to uniquely identify an instance of Preferred Merchant Lists. The client should not generate the hash key value. Instead, the client should query on the Preferred Merchant Lists collection resource with a filter on the primary key values in order to navigate to a specific instance of Preferred Merchant Lists.
For example: preferredMerchantLists?q=ExpenseTypeId=<value1>;MerchantListType=<value2>;StartDate=<value3>
Query Parameters
-
dependency: string
This parameter specifies dependencies which are fields that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The fields specified in this parameter are always set in the resource instance in question. When a child resource collection is requested and the parameter is set, the fields will be set in the parent resource instance before generating the resource collection payload. The value of this query parameter is a set of dependency fields. Example: dependency=ProductId=2
Format: <attr1>=<val1>,<attr2>=<value2> -
expand: string
When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
-
fields: string
This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.
Format: ?fields=Attribute1,Attribute2
Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2 -
links: string
This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>
Example:
self,canonical -
onlyData: boolean
The resource item payload will be filtered in order to contain only data (no links section, for example).
Header Parameters
-
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.
There's no request body for this operation.
Back to TopResponse
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 : expenseTypes-preferredMerchantLists-item-response
Type:
Show Source
object
-
CreatedBy: string
Maximum Length:
64
User who created the preferred merchant list. -
CreationDate: string
(date-time)
Date when the preferred merchant list was created.
-
DispWarningToUserFlag: boolean
Maximum Length:
1
Indicates whether policy warning is displayed to user. -
EndDate: string
(date)
Date when this preferred merchant list is no longer applicable.
-
ExpenseTypeId: integer
(int64)
Value that uniquely identifies the parent expense type.
-
LastUpdateDate: string
(date-time)
Date when the preferred merchant list was last updated.
-
LastUpdatedBy: string
Maximum Length:
64
User who last updated the preferred merchant list. -
LastUpdateLogin: string
Maximum Length:
32
Session login that is associated with the user who last updated the preferred merchant list. -
links: array
Links
Title:
Links
The link relations associated with the resource instance. -
MerchantListName: string
Read Only:
true
Maximum Length:80
Lookup type name that provides name of the preferred merchant list. -
MerchantListType: string
Maximum Length:
30
Lookup type code of the preferred merchant list. -
PolicyEnforcement: string
Title:
Meaning
Read Only:true
Maximum Length:80
Type of policy enforcement applied to this preferred merchant list. Values are from lookup EXM_PREFERRED_ENFORCEMENT. -
PolicyEnforcementCode: string
Maximum Length:
30
Code of policy enforcement applied to this preferred merchant list. Values are from lookup EXM_PREFERRED_ENFORCEMENT. -
StartDate: string
(date)
Date when this preferred merchant list is applicable.
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.