Disable All Advertising
Image
EAN-130000002084145   EAN-13 barcode 0000002084145
UPC-A000002084145   UPC-A barcode 000002084145
Product NameEss Cdi Rx Insert Lenses Esgcdrxli
CategoryFood
Short Description06 Ct
Amazon.comA Buy on Amazon ~ B001BK6AWU
Long DescriptionFor those with prescription eyewear, ESS has the solution. After lenses have been corrected by an optometrist and fit into the CDITM Rx Inserts, these low-profile, Rx integrations slide into the CDITM like any other replacment lens. One set contains two lens inserts. CDITM sunglass sold separately. Important safety note for CDITM sunglass users operating in proximity to fragmentation hazards: ESS strongly recommends the use of high-impact polycarbonate prescription lenses to optimize impact resistance in the CDITM sunglass. Due to the variability of prescription lens shapes, materials, and thicknesses, it is impracticable to determine if the sunglass system is compliant with the ANSI Z87.1 and MIL-PRF-31013 spectacle impact standards when prescription lenses are installed. High-impact polycarbonate prescription lens material will maximize the impact resistance of the system well beyond that offered by CR-39 resin or other common materials used in prescription lens manufacturing.
Created07-01-2006
Modified06-29-2020 4:08:38am
MD5f5b2e62eac26b70f91117e7220109294
SHA2562e281d197bb9b77caa65a759bf9f6f8410defa748edede064c57162bf0f42972
Search Googleby EAN or by Title
Query Time0.0050681

An article of interest

Making use of the tools we offer

Data Feed API - Extra

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.