Most feed registration issues are caused by multiple repeating XML elements of the product element (e.g. multiple image resolutions) confusing the auto-detection logic (which looks for the most repeating element in the XML). For example, on Feed Registration Step 1, if you sse something like the following in the auto-detected format string box:
xml|PRODUCTS/PRODUCT/IMAGES/IMAGE/
....that would need to be edited down to just:
xml|PRODUCTS/PRODUCT/
(and then click Next to go to step 2)
Another possibility is that on Feed Registration Step 2 the auto-selection logic has picked an incorrect field for one or more of the required fields. For example, if the script sees a field called PRICE it will automatically map that field to Price but the actual price field might be PRICE/BUYNOW. To double check, refer to the Sample Data shown below the form to confirm that the fields being selected show valid data alongside...
Hi,
Most feed registration issues are caused by multiple repeating XML elements of the product element (e.g. multiple image resolutions) confusing the auto-detection logic (which looks for the most repeating element in the XML). For example, on Feed Registration Step 1, if you sse something like the following in the auto-detected format string box:
xml|PRODUCTS/PRODUCT/IMAGES/IMAGE/....that would need to be edited down to just:
xml|PRODUCTS/PRODUCT/(and then click Next to go to step 2)
Another possibility is that on Feed Registration Step 2 the auto-selection logic has picked an incorrect field for one or more of the required fields. For example, if the script sees a field called PRICE it will automatically map that field to Price but the actual price field might be PRICE/BUYNOW. To double check, refer to the Sample Data shown below the form to confirm that the fields being selected show valid data alongside...
Cheers,
David.
--
PriceTapestry.com