 Otto
|
Hello,
You don't have to import the main price, but two custom fields related to the secondary currency:
_regular_price_USD
_price_USD
Both fields should have the same value.
In the test site, the main price is in Euros.
Best Regards,
Otto
|
 davidH-172
|
I have no also tested importing both _regular_price as well as _regular_price_usd together (two fields) and the sqme behaviour persists.
Are we able to escilate this in some way. It seems a clear and obvious bug if the data imports, and can be seen, but required you to manually edit the product and click update.
|
 Otto
|
Hello,
Thanks.
I've escalated the issue to our compatibility team. I'll get back to you as soon as we have news.
Best Regards,
Otto
|
 davidH-172
|
Is there an update. The support has honestly been shockingly bad with this issue.
|
 Otto
|
Hello,
I got a reply from the second-tier:
I was able to update a product, and the new price was showing on the frontend without updating the product.
In the Import settings, I added regular_price_USD, price_USD, wcml_custom_prices_status and _sku
In the template, I added _sku in the WooCommerce Add-on just to have a piece of content updated that is not a custom field
The first import was skipped because it was identical to the previous one, so I uploaded a new file where the price was 110
On the second import, the product got updated in the backend and the frontend
Video: hidden link;
But as you can see in the video, they were changing the currency settings also, so I asked for confirmation without doing that, and I just got this reply:
hidden link
Can you please give it a try?
Best Regards,
Otto
|