Hi Nilesh,
Is it this step in the product flow that is deleting metafields that aren't mapped?
If so, couldn't we just put a filter on it to not let any records flow into it?
Or does this have nothing to do with the current GraphQL issue?
Hi @coryanderson The Delete Metafields in Shopify bubble is not responsible for deleting metafields that are not mapped (in)correctly in the Post Products to Shopify bubble.
This deletion behavior occurs because we are using the productSet mutation. We will address this metafield deletion use case in the integration application by March 18, 2025. After this update, any metafields that are not mapped in IA, not configured in settings, or not included in the NetSuite saved search will be retained in Shopify.
No action will be required from customers.
Cc @sandrahill @David_C .
Thanks
Nilesh.
HI @nileshkumar
Are you able to confirm that the patch will address the issue for both Product and Variant meta-fields?
Kind regards
Sandra
That is correct understanding @sandrahill . The patch will address metafield deletion issue for both product and variant.
Thanks
Nilesh.
We are having the same struggle and Shopify is pulling in an engineer to help us since the scripting they are using isn't populating the cost field as expected. Ticket number 241779. Apparently they have to pull them in to a meeting next week with us from India, so scheduling is where we are at with it.
Look at this mapping. From his response it sounded like Jason was able to get it working by switching from number to string.
Thanks @nileshkumar I'm sure you had reasons for moving the conversation to a different platform, but man it's a PIA to have another location to go find conversations related to KB articles, and vice versa.
Correct, our mapping is working correctly and flowing data as expected.
Is this still on schedule to be fixed by tomorrow? So when I log in tomorrow the IA will be updated?
1 Like
Nope it is not. Or wasn't I guess. Past tense since it's the 18th now.
@nileshkumar What is the update on this fix? I tested this morning (March 18) and the graphql flow is still deleting metafields.
Looks like we might have more time. Celigo's docs now show July 1, 2025 as upgrade timeline (previously April 1).
As far as I know, the fix was rolled out to a small numbers of accounts, mine being one of them, but there were issues (related to SEO fields and undefined meta data created by 3rd party apps) so now they are working on a fix for the fix. This is due to be completed tomorrow, according to support.
1 Like
Yes we have an extension until July 1st now.
1 Like
2 Likes
Hi All,
This fix is now pushed to all accounts! Customers will no longer face issues related to the deletion of metafields.
Additionally, we are introducing a new way to map metafields. While the previous mapping method remains functional, the new approach in GraphQL aligns closely with how metafields were being mapped for Variants. This means that the NetSuite Saved Search needs to follow a specific format for both product and Variant, and an additional mapping update is required in the Product flow, making it more streamlined and easy to use.
Detailed steps can be found under Map metafields at product level using the saved search.
Please refer the section Mapping NetSuite Standard/Custom fields to Shopify metafields (recommended approach) mentioned in the KB Article.
Thanks
Nilesh.
3 Likes
Just a quick update from me - we have now managed to fully migrate our product flows to GRAPHQL including managing specific product and variant metafields via saved search.
I did have to remove the product metafield definitions from the settings section (they had been required previously) to get this to work - but had to leave in the variant ones.
Thanks to @nileshkumar and the Celigo team for resolving this.
3 Likes
Hi Nilesh,
I'm finally working with my customer that maps metafields and converting them to GraphQL.
They are currently using the settings based metafield system. The article outlining steps to move to GraphQL still recommends this method. You seem to be recommending the saved search method.
What's the best way to go?
Here's what the GraphQL conversion article states:
Hi @davidgollom
Glad to see you're prioritizing the migration of product flows to GraphQL with the June deadline approaching.
For syncing metafields:
- Use the setting approach if Handlebars aren’t needed.
- Use mapping if Handlebars are required.
I've updated the KB article to reflect this.
Thanks for bringing it to our attention!
Nilesh.
1 Like
Also if you have any trouble with variant fields on the non-matrix products in Shopify this is definitely the way to go. It doesn't allow any editing of the value (unless you are in a flow you can add transformations/scripts to, but it works well for us as long as the field coming from Netsuite isn't a value from a list. Otherwise at the moment it just returns the internal id not the actual value but I think that is being fixed in July.
1 Like