Skip to main content
Answer

Shopify Metafield Data Loss with 25R1 Shopify Connector — Is This Happening to Others

  • September 9, 2025
  • 7 replies
  • 133 views

Forum|alt.badge.img

Hello Acumatica Community!
 

We’ve run into a not good experience, issue with the latest Shopify connector for Acumatica (25R1). I’m hoping to get some insights from others who might be experiencing the same or confirm if this is an isolated problem on our end.

What we observed

Background: We rely on metafields in Shopify and map another metafield from a Stock Item attribute via the connector.

Normal behavior (pre-25R1): If a value existed in Shopify for one metafield, and another metafield was mapped from a Stock Item attribute, the “unmapped” metafield retained its value while the “mapped” metafield was updated as expected.
 

Current issue (25R1): The connector now tries to update each metafield. And if there’s no mapped attribute for a metafield, connector clears it. This results in unintended data loss across the board, not just the mapped fields.
 

Has anyone else experienced metafield data being cleared or reset by the 25R1 Shopify connector?

Best answer by KarthikGajendran

@jib87 ​@clancour  We acknowledge that this is indeed an issue, which occurred during the migration from the Shopify REST API to the GraphQL API.

The issue has been resolved in 25R1, and you should receive the updated version on October 29th.

Thank you very much for your patience and understanding.

7 replies

Forum|alt.badge.img
  • Jr Varsity II
  • September 23, 2025

@jib87 

Yes, we have a client experiencing this as well.

We have tried <<unmap» as well - same behavior. 

Similar thread:

Opening a case with support now.


KarthikGajendran
Acumatica Moderator
Forum|alt.badge.img+3
  • Acumatica Moderator
  • Answer
  • October 7, 2025

@jib87 ​@clancour  We acknowledge that this is indeed an issue, which occurred during the migration from the Shopify REST API to the GraphQL API.

The issue has been resolved in 25R1, and you should receive the updated version on October 29th.

Thank you very much for your patience and understanding.


PatrickSchlenker90
Varsity III
Forum|alt.badge.img+1

Hi ​@KarthikGajendran 

is there a suitable workaround for customer who run into this issue? As ​@clancour mentioned, it seems like no possible solution to unmap…

Best regards, Patrick


KarthikGajendran
Acumatica Moderator
Forum|alt.badge.img+3

@PatrickSchlenker90 Could you please let me know which version you are having this issue? Is it 25R1?


KarthikGajendran
Acumatica Moderator
Forum|alt.badge.img+3

@PatrickSchlenker90 ​@clancour ​@jib87 This is fixed in 25R1 and 25R2 and 26R1. Please upgrade to the latest version. 

If for some reason you cannot upgrade immediately, then please let me know.


PatrickSchlenker90
Varsity III
Forum|alt.badge.img+1

@PatrickSchlenker90 Could you please let me know which version you are having this issue? Is it 25R1?

Hi ​@KarthikGajendran 

we are currently on 25.101.0204 and to upgrade to the fixed version “25.101.0224” (2025R1 Service Pack 1 Patch 4) will be a big effort for us.

If for some reason you cannot upgrade immediately, then please let me know.

is there a way to fix the issue within an customization, so we are able to deploy the fix only to the needed instances?


KarthikGajendran
Acumatica Moderator
Forum|alt.badge.img+3

@PatrickSchlenker90  Please try to use the attached customization and let me know if it solves your issue.