-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
422 on Products #2
Comments
Have you tried it more than once? We've seen a few images fail over time, breaking the product import. Running it a second time might do the trick, and wouldn't import already-imported products |
Perhaps it is related to the number of metafields on these products or the content within them, from another store with less metafields I am not having that problem. |
(Sorry, I somehow did not get a notification when you answered!) |
I was curious if it was the metafields that are filled by Okendo (reviews app) that have HTML and are super long, but ignoring them/all the metafields did not resolve the issue.
I was able to duplicate the products from one store, but not another. I’ll keep trying to hunt down what is triggering the 422 entity not processed error.
I see that gift cards aren’t working, but in this case it seems to be more all products or none are working. Collections are working fine…
I’ve seen that there could be issues with particular values triggering this error, like if the Compare At price is lower than the Sale Price, and those sorts of things - so it may just be that there’s an invalid value on a particular field that validates in the shopify dashboard but not in the API.
…On Mar 20, 2021, 10:15 AM -0400, Alex Leclair ***@***.***>, wrote:
(Sorry, I somehow did not get a notification when you answered!)
Interesting; The amount of metafields shouldn't matter. Do these products have anything in common (ex: are they gift cards?).
Creating gift cards through the API is currently not supported, so that could explain it...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Oh! You are totally right! It could absolutely be a |
Aha! I found it, the fulfillment service is not created in the staging environment so the product cannot be created.
What got me there was adding `console.log(e.response.body)` on line 284 of migrator.js
…On Mar 20, 2021, 10:28 AM -0400, Alex Leclair ***@***.***>, wrote:
Oh! You are totally right! It could absolutely be a compare_at_price issue.
If you're feeling adventurous, you could open up shopify-api-node in node_modules and add a console.log to the value of "body" in this file; it should show what the actual error is, and help solve this :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I was able to fix it for me, but I'm not sure it's a full solution, so I added at line 172 of migrator.js
|
Very very very good find! That's definitely a good interim solution :-) |
After running
yarn start --products
each product fails to import to an empty destination store and there is a http 422 error which I can see after adding a console log. I double checked the permissions on both stores andyarn start
returns "Store configuration looks correct."I'm guessing there's an issue with line 174 of migrator.js and the structure of the product object
const newProduct = await this.destination.product.create(product)
The text was updated successfully, but these errors were encountered: