eLink retailmax.elink.products

{ "RootType":"ARAY",
  "DATS":[ 
	{
	  "Pid":100,
	  "Description":"Example Product",
	  "Price":9.950000,
	  ...
	}
]}

Input Arguments

Output Fields

Field#	Name	Datatype	Flags	Description
f100	Pid	Number	Present Selectable	The product id (pid) for this record. Zero will not be a pid value. The number itself has no meaning, it is just a unique identification number
f101	Description	String	Present Selectable	Product Description
f103	Price	Yes	No	Unit Price. The basic list retail price of this item. This is not necassarily the price that will be charge to customers, as many other factors affect final customer pricing.
f104	Spid	Yes	No	Last Supplier id
f105	PLU	Yes	Yes	PLU code assigned to this product
f106	Depid	Yes	No	Department id
f108	LastCost	Yes	No	Last Cost Price
f198	Publish	No	Yes	Publish indicator. This indicator is set non-zero when this item can be published to external users, such as web servers. The use of the publish indicator is optional and web servers are still free to query any product that security settings permit.
f500		No	Yes	Combination search field. If a predicate is searched against this field the system will internally query several fields, which can be easier than specifying each field to be searched individually. If supplied in a selection predicate then the output will contain a sensible product description type field(s)
f510	UpSize	No	No	Pid of a product (f100) considered to be bigger than this prouct. This is the upsize for this product.
f511	DownSize	No	No	Pid of a product (f100) considered to be smaller than this prouct. This is the downsize for this product.
f512		No	No	Return extended pricing information for this product. As this information is more complex than a single field value, you request field 512 to be returned and the server will return an APPT packet with extending pricing information. See the examples below.

This bucket also includes the GDS Retail Item universal object fields. This means that the fields that are present in this common definition can also be present in this bucket. Where GDS fields are used, they are mapped by adding 8388608 to the GDS field# to get a value for this buckets output record. For example, GDS Field# 200 becomes (8388608 + 200 = 8388808).

Examples

/gnap/buck?3=retailmax.elink.products&9=f500,8,ab Returns details of products that have "ab" in one of several fields, such as description or PLUcode

/gnap/buck?3=retailmax.elink.products&9=f100,0,7&11=debugset3&10=8390617,8390716-8390718,8391117,8391608-8391616,8392117 Request specific fields for a single product. (This record is retrieved from a test reference database)

Request pricing information for product #37: /gnap/buck?3=retailmax.elink.products&9=f100,0,37&10=512

 <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> 

 <ARAY>
 <DATS>
  <f100>37</f100> 
  <f101>Logbook 50 form duplicate</f101> 
  <f103>7.2000</f103> 
  <f104>12</f104> 
  <f105>LB2</f105> 
  <f106>3</f106> 
  <f108>3.4000</f108> 
 <APPT>
  <f3>21</f3> 		// Constant for pricing information
  <f2>5</f2> 		// Constant for pricing information
  <f101>37</f101> 	// Product id.  Will match f100
  <f100>5</f100> 	// Internal pricing id
  <f103>1</f103> 	// Minimum quantity required to get this price
  <f105>7.200000</f105> 	// Price
  </APPT>
 <APPT>
  <f3>21</f3> 
  <f2>5</f2> 
  <f101>37</f101> 
  <f100>6</f100> 
  <f103>10</f103> 
  <f105>6.500000</f105> 
  </APPT>
  </DATS>
  </ARAY>