Solved

A child stock-item attribute should synchronize to the corresponding Shopify variant metafield.-Not working

26 days ago
September 18, 2026
5 replies
100 views
Translate All

Adcirruserp
Freshman I

I am working on a Shopify integration involving template items and their child stock items.

The customer maintains Color and Size as product attributes. In addition, they use a Shopify color metafield for business verification. This metafield is configured as a single-choice text field with a predefined drop-down list, allowing the user to select one color.

I created a corresponding attribute in Acumatica and tested both Combo and Multi Select Combo control types. I also configured entity mapping to export the attribute value from Acumatica to the Shopify metafield.

Best answer by Saikrishna V

@Adcirruserp

The standard entity mapping approach mentioned above is worth trying first. However, if you want to handle this through customization, you can extend SPTemplateItemProcessor.

Override MapBucketExport and execute the standard export first.
Access the Shopify variants through bucket.Product?.Extern?.Variants.
Match the Shopify variant with the corresponding Acumatica matrix/child stock item using the SKU.
Read the child item's attribute value from AttributesValues.
Update the corresponding variant.VariantMetafields.
Since the Shopify metafield is a list type, serialize the value as a JSON array.

public delegate Task MapBucketExportDelegate(SPTemplateItemEntityBucket bucket, IMappedEntity existing, CancellationToken cancellationToken);

[PXOverride]
public async Task MapBucketExport(SPTemplateItemEntityBucket bucket, IMappedEntity existing, CancellationToken cancellationToken, MapBucketExportDelegate baseMethod)
{
    await baseMethod(bucket, existing, cancellationToken);

    ProductDataGQL external = bucket.Product?.Extern;

    if (external?.Variants == null)
        return;

    foreach (ProductVariantGQL variant in external.Variants)
    {
        // Match Shopify variant with Acumatica matrix item using SKU.
        // Read the corresponding child item attribute from AttributesValues.
        // Update the Shopify variant metafield.

        string value = JsonConvert.SerializeObject(new[] { attributeValue });

        MetafieldGQL metafield = variant.VariantMetafields?.FirstOrDefault(x =>
            x.Namespace == "custom" &&
            x.Key == "varaint_level_color");

        if (metafield != null)
            metafield.Value = value;
    }
}

Hope this helps!

View original

michaelho
Semi-Pro III
26 days ago
September 18, 2026

@Adcirruserp this mapping would need to be added to the Template Item entity, and the External Object should be Product → Product Variants → Metafields and the ERP Object should be Template Items → Matrix → Attributes:

Translate

Steve Milner
Varsity III
26 days ago
September 18, 2026

@Adcirruserp Michael's mapping is the right one. With Product -> Product Variants -> Metafields as the target and Template Items -> Matrix -> Attributes as the source, the connector matches each matrix item to its Shopify variant by SKU and writes that child item's attribute value to that variant. Your row pointed at Product -> Metafields, which writes to the product and never reaches the variant definition.

One more thing to check once you've switched it. Your Shopify screenshot shows the metafield as Single line text (List). You described it as single choice, but a list definition is a different type. Through the API, Shopify only accepts a JSON array for a list metafield, something like ["Blue"]. The connector reads the type from your Shopify definition and sends the attribute value as plain text. If your client only ever picks one color per variant, set the metafield up as one value rather than a list, and use a plain Combo attribute in Acumatica. Multi Select Combo isn't needed for that.

Also compare the two value lists. You have Gray in Acumatica and Grey in Shopify, and the target field has to be namespace.key spelled exactly as Shopify has it, so custom.varaint_level_color if that typo is in the definition too.

Try it on one template item and look at the variant in Shopify before you resync the rest.

Translate

Steve Milner - Acumatica Consultant, Acumaven Inc. | acumaveninc.com | linkedin.com/in/steve-milner-52654b3

Adcirruserp
Author
Freshman I
25 days ago
September 19, 2026

@Steve Milner Getting this error.

(field: input.variants.0.metafields.1.value) Value is invalid JSON: unexpected character: 'Blue' at line 1 column 1.

Translate

Saikrishna V
Captain II
Answer
23 days ago
September 21, 2026

@Adcirruserp

The standard entity mapping approach mentioned above is worth trying first. However, if you want to handle this through customization, you can extend SPTemplateItemProcessor.

Override MapBucketExport and execute the standard export first.
Access the Shopify variants through bucket.Product?.Extern?.Variants.
Match the Shopify variant with the corresponding Acumatica matrix/child stock item using the SKU.
Read the child item's attribute value from AttributesValues.
Update the corresponding variant.VariantMetafields.
Since the Shopify metafield is a list type, serialize the value as a JSON array.

public delegate Task MapBucketExportDelegate(SPTemplateItemEntityBucket bucket, IMappedEntity existing, CancellationToken cancellationToken);

[PXOverride]
public async Task MapBucketExport(SPTemplateItemEntityBucket bucket, IMappedEntity existing, CancellationToken cancellationToken, MapBucketExportDelegate baseMethod)
{
    await baseMethod(bucket, existing, cancellationToken);

    ProductDataGQL external = bucket.Product?.Extern;

    if (external?.Variants == null)
        return;

    foreach (ProductVariantGQL variant in external.Variants)
    {
        // Match Shopify variant with Acumatica matrix item using SKU.
        // Read the corresponding child item attribute from AttributesValues.
        // Update the Shopify variant metafield.

        string value = JsonConvert.SerializeObject(new[] { attributeValue });

        MetafieldGQL metafield = variant.VariantMetafields?.FirstOrDefault(x =>
            x.Namespace == "custom" &&
            x.Key == "varaint_level_color");

        if (metafield != null)
            metafield.Value = value;
    }
}

Hope this helps!

Translate

SaiKrishnaV | https://www.linkedin.com/in/saikrishna-vaddepalli-aa67b8225

Steve Milner
Varsity III
23 days ago
September 21, 2026

@Adcirruserp that error is the list type. The mapping is working now: the connector found the variant and sent Blue to the right metafield. Shopify rejected it because the definition is Single line text (List), and a list metafield has to arrive as a JSON array like ["Blue"]. The connector sends the attribute value as plain text, so Shopify tries to read Blue as JSON and stops at the first character.

You have two ways out, and which one depends on your client. If a variant only ever has one color, set the metafield up in Shopify as one value instead of a list, keep the same preset choices, and point the mapping at that namespace.key. No code, and the Combo attribute goes across as is.

If your client needs it to stay a list, the standard mapping won't get you there and Saikrishna's approach is the route: extend the template item processor and serialize the value as a JSON array before it goes out. That's a customization project, so build and test it against a development store first.

Either way, test one template item and check the variant in Shopify before you resync the rest.

Translate

Steve Milner - Acumatica Consultant, Acumaven Inc. | acumaveninc.com | linkedin.com/in/steve-milner-52654b3

About Acumatica ERP system

Acumatica Cloud ERP provides the best business management solution for transforming your company to thrive in the new digital economy. Built on a future-proof platform with open architecture for rapid integrations, scalability, and ease of use, Acumatica delivers unparalleled value to small and midmarket organizations. Connected Business. Delivered.

Sign up

Social Login

Login to the community

Social Login