EAN-130000000000079   EAN-13 barcode 0000000000079
UPC-A000000000079   UPC-A barcode 000000000079
UPC-E00000709   UPC-E barcode 00000709
Product NameHolster Work Trouser & Knee Pads 34in
CategoryHome
Amazon.comA Buy on Amazon ~ B00014328W
SKU8300-SR1-20041
Width13.78 inches    (convert)
Height0.71 inches    (convert)
Length21.65 inches    (convert)
Weight41.6 ounces    (convert)
BindingKitchen
Long DescriptionThe Roughneck Black & Grey Holster Work Trouser have been designed to meet the needs of everyday use. They are made from 280gsm polyester cotton twill, with Cordura reinforcement on the knee pad pockets, back of the trouser hem and holster pockets. Cordura is a hardwearing fabric designed to withstand everyday use. The trousers have a with reinforced crutch and YKK zip and zip pull for easy operation. The Holster Trousers have many pockets including: Two holster pockets.Two front pockets. Two hook and loop rear pockets. A multi left leg side pocket with hook and loop pocket. Separate pocket for mobile phone storage secured by hook and loopRight leg pocket with hook and loop flap. Supplied with Roughneck Knee pads are made form 100% Polyethylene with an ergonomic shape for comfort and flexibility. They are the perfect fit for the Roughneck Holster trousers and can be used with Roughneck work trousers.These Holster Trousers have the following specifications: Waist: 34 inches.Leg: 31 inches. Holster Work Trouser & Knee Pads 34in
Created01-10-2013 9:03:48am
Modified11-20-2017 1:48:26am
MD5be2612f55f1054a6a7ffad6de4882417
SHA25632733fd24209a9370d1d4ff312b80b31ed9bb01969cce5bb4af661a45c2679d3
Search Googleby EAN or by Title
Query Time0.0002289

The extra items are numerically indexed and provide extra text to go along with numeric values such as weights or distances or even currencies. The attributes that use these extra indexes are all numeric and take two fields. You can send the data in a single field as long as you use the same short or long text that we keep in our database.

Although the data feed API can deliver information as JSON or XML, we are using XML here because it is easier to read.

<attribute>
   <extra_group>Distance</extra_group>
   <field_name>depth</field_name>
   <extra>
      <id>501</id>
      <extra_short>in</extra_short>
      <extra_long>inches</extra_long>
      <seq>10</seq>
   </extra>
   <extra>
      <id>503</id>
      <extra_short>ft</extra_short>
      <extra_long>feet</extra_long>
      <seq>20</seq>
   </extra>
   <extra>
      <id>505</id>
      <extra_short>yrd</extra_short>
      <extra_long>yards</extra_long>
      <seq>30</seq>
   </extra>
</attribute>

Looking at this example, you can see that the EXTRA portion is an array of values each with their own properties. Here is what each section means:

This extra information is normally used in a drop down box next to the numeric data field that we want to enhance. Some examples might be:

You see we can display the long or short version of the extra code by using the ID index.

Fields that make use of this extra information require it when pushing data back to us in the feed. You can either send the data in two fields (value and extra_id) or in a single field (value) as long as the text following the numeric portion matches the long or short version of the extra data we store for the field.

For example, if you wanted to update a field that represented distance with the value "100 yards", you could either send that data just like that in the value field value=100+yards or in two seperate fields value=100&extra_id=505 and you would get the same results. If you send an invalid extra_id or text after the number that doesn't match our accepted list, your update would be rejected.

Close

Search

Close

Share

Close

Dialog