We had this issue during the original rest>graphql set up and switch but it seems that again we have products that are not getting inventory status tracked field set. Even if I hard code a value in the mapping it is being ignored.
It sends it as false, even though our data from Netsuite and mapping are set for it to be true.
Has anyong begun encountering this again? I am worried that the update Monday morning (on a holiday for some reason???) reverted code in the hooks or caused a new issue.
We are testing now but might possibly have it working. Essentially just redid the exact same mapping. I am not sure why that would have anything to do with it but it is mapping correctly now. Will update this post when our flow completes and I see if it actually did it.
This field previously was essentially irrelevant to what we mapped though because it’s the inventory tracked field that is handled by a Celigo hook. I know during setup we could hard map it and it didn’t do anything. So possibly it was previously not even looking at the field in the mapping, and only looking at the field coming in from NS, but now after the update it is actually looking at the mapping.
Could the code to handle inventory tracking have been updated to more accurately reflect the current shopify/graphql schema and no longer be using the hook code from the rest flows?
Is it common to do IA updates on federal holidays so when it breaks something that previously worked, it runs for 24 hours before we notice it’s set hundreds of items incorrectly?
It looks like it was in fact updated to start looking at mapping. Ultimately that is good and preferred. Are you able to confirm when that update itself was actually pushed live?
If it happened yesterday then it seems that the update was made and the older functionality was deleted which caused all the errors. Is that what the cause was?
Hi @craigscott , as support already confirmed we pushed the update for syncing tracked inventory on September 1st to few accounts including yours . Previously, IA directly fetched data from NetSuite, but now it respects your configured mapping. We did not alter existing inventory tracking mappings, we only added mappings if none were present - This was called out in the KB article as well.
The error experienced by you was due to the incorrect mapping, which you already corrected.
Thank you for your feedback. Moving forward, our team will ensure future release dates do not coincide with holidays.
Right, I get that mapping wasn’t altered which I understand. What I am confused about is that I do not believe any mapping was even needed beforehand because of the IA fetching the data from NS. It was handled in the background. We had that mapping leftover from trying to get it to work months ago before we learned about the NS/IA data fetching.
What we are frustrated with is that the old functionality was removed at the same time the new was added. And due to us having some leftover mapping, mapping we left because we didn’t think it mattered or was being used at all, and didn’t know had a formatting/logic error, it caused our inventory tracking to fail.
I do appreciate the team getting quick answers to us both here and in the ticket though.
Was there a email alert or anything that I missed regarding this functionality being removed and changed?
Release notes are shared before every release cycle, providing a high-level overview of enhancements, fixes, and newly introduced features. The KB link you shared captures all the changes made as part of August release for Shopify IA.
