Originally Posted by
jeking
I edited the file as you indicated, added the field in the configuration but not sure this is the result we need.
Originally Posted by
jeking
User Defined Products Fields:
products_price_w: TRUE
options_values_price_w: FALSE
I did an export and the options_values_price_w column is not in the Detailed Products Attributes file.
Did I misunderstand something you said?
Originally Posted by
jeking
Too late to edit.....hold on, editing error on my part. Update to come....
Understand that more is likely to come, but would like to go ahead and cover what has been already "discussed".
So I didn't correct the attempt to use the User Defined Products Fields for an attribute field, which would be why the above "FALSE" occurred, because that field (options_values_price_w) does not exist in the products table. (Sure someone could add it, but it is not the field in question.)
So then the desire is to work with that field which has been identified as working with the module titled "Dual Pricing". As such, in the list of Custom Products Fields, if the options_values_price_w field is identified in the products_attributes table, then a TRUE will be shown. Ie.:Product Short Descriptions: FALSE
Product Unit of Measure: FALSE
Product UPC Code: FALSE
Google Product Category: FALSE
Manufacturer's Suggested Retail Price: FALSE
Manufacturer's Advertised Price: FALSE
Group Pricing Per Item: FALSE
Exclusive Products Mod: FALSE
Stock By Attributes Mod: FALSE
CEON URI Rewriter Mod: FALSE
Dual Pricing Mod:TRUE
With that shown as TRUE, the field is expected to be included in the exported attribute_detailed file and with the correction applied above that same system could process a detailed attribute file that does not have the field and the field would remain unchanged. If the change is not applied, then the field would need to remain present when importing or else the field would become blank for each successfully processed row.
Bookmarks