Customer Feedback
We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.
For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.
Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.
This should be reopened, as while you can run the refresh published products, it doesn't work in local or QA environments.
Hi Arthur,
I was able to test this today. It does seem to let me run refresh published products on sandbox when prod is syncing approvals. However, it gives a lot of messages like this:
Unable to find any Categories within Commerce for PIMCategoryId: f0dc5bc4-a43f-11eb-8c15-37951e3b0982
So I'm not sure it's actually updating anything.
Hi Scott,
No worries - let us know when you get a chance to test this. This should work as you expect but I'll wait to get confirmation from you.
Hi Arthur,
I haven't forgotten about this one. I have a specific project I wanted to test it on, but they are switching domain names, so I need to wait for that to go to prod (its a separate category tree) before I try it. Will get back within 2 weeks.
Hi Scott,
We should have fixed that issue with a change we made in Q3 of 2021. We changed the integration job so it matches on the website name rather than the ID to avoid this issue when switching publishing environments. As long as the website's have the same name between environments this should work. Could you send the error message you're seeing with the refresh?
Hi Arthur,
It does fail, but I think it's because the website GUIDs are different between sandbox/prod.
Hi Scott,
The active publishing environment setting is specific to the publish job. This setting does not affect the refresh job and you can run the refresh in your sandbox or other secondary environments without changing the active publishing environment setting. Typically, this setting is only changed once during an implementation when you are ready to go live. At that point you set Production as the publishing environment, enable publish in production, disable publish in sandbox, and if desired, configure the refresh job to keep data up to data in sandbox.
Could you verify if the refresh job fails to run in sandbox with the active environment set to production?
-Arthur
Hi Arthur,
Could you clarify this a bit more? We just tried this the other day and it didn't work.
Use case:
1. We have approved products getting published in production. Everything is working great.
2. We want to refresh sandbox to get recently added data.
Currently I have to switch to "sandbox' environment in PIM settings, run the Sync job, switch the category tree to pint to the sandbox websites, then run the refresh published products in sandbox. Meanwhile, production isn't getting updates and we have the PIM users pause all approvals until we are done.
Are you saying that we don't need to follow these steps anymore?
Hi Scott,
We made an update to the refresh job that allows you to pull product data for any status (previously it only worked for products with published status). With this change, you can now pull data to secondary environments that have not yet been published to production using the refresh job - so it will not cause the status of the products in PIM to change.
Does this satisfy the request here or are you looking for additional capability?
-Arthur