Diagnose a missing Store global attribute through group and family mappings
Trace one Store global attribute through its definition, localized label, group, family, and entity mappings. Keep this diagnostic separate from product PIM metadata.
In this guide
Start with the Store form
A Store setting exists in metadata but does not appear on the intended Admin form. First distinguish a missing field from a visible field with an empty value. The definition, locale, group, family, and Store entity relationship all need to match the form being inspected.
Use the fictional GcgSupportLabel attribute from the Store SQL migration recipe. Select the intended Store group and family explicitly. Do not apply the field to every family as a troubleshooting shortcut. Product PIM attributes have a separate diagnostic path described in the product-attribute migration guide.
Resolve one intended relationship path
The query below follows only the Store global-attribute domain. Set the locale, group, and family codes to the actual intended configuration. LEFT JOIN preserves the definition when an expected edge is absent, making missing relationships visible as null columns. If there is no Store definition at all, the query returns no rows.
Multiple rows can indicate duplicate definitions, labels, or mappings. Investigate the individual relationship counts before changing data. Do not select the first result or treat a broad join count as proof of a unique attribute.
inspect-store-global-attribute-mapping.sql sql
DECLARE @AttributeCode nvarchar(300) = N'GcgSupportLabel';
DECLARE @GroupCode varchar(200) = 'GcgContent';
DECLARE @FamilyCode varchar(200) = 'Store';
DECLARE @LocaleCode nvarchar(50) = N'en-US';
SELECT a.GlobalAttributeId, a.AttributeCode,
l.GlobalAttributeLocaleId, l.AttributeName,
g.GlobalAttributeGroupId,
ag.GlobalAttributeGroupMapperId,
f.GlobalAttributeFamilyId,
fg.GlobalFamilyGroupMapperId,
ge.GlobalGroupEntityId
FROM dbo.ZnodeGlobalEntity AS e
JOIN dbo.ZnodeGlobalAttribute AS a
ON a.GlobalEntityId = e.GlobalEntityId
LEFT JOIN dbo.ZnodeLocale AS loc
ON loc.Code = @LocaleCode AND loc.IsActive = 1
LEFT JOIN dbo.ZnodeGlobalAttributeLocale AS l
ON l.GlobalAttributeId = a.GlobalAttributeId AND l.LocaleId = loc.LocaleId
LEFT JOIN dbo.ZnodeGlobalAttributeGroup AS g
ON g.GroupCode = @GroupCode AND g.GlobalEntityId = e.GlobalEntityId
LEFT JOIN dbo.ZnodeGlobalAttributeGroupMapper AS ag
ON ag.GlobalAttributeGroupId = g.GlobalAttributeGroupId
AND ag.GlobalAttributeId = a.GlobalAttributeId
LEFT JOIN dbo.ZnodeGlobalAttributeFamily AS f
ON f.FamilyCode = @FamilyCode AND f.GlobalEntityId = e.GlobalEntityId
LEFT JOIN dbo.ZnodeGlobalFamilyGroupMapper AS fg
ON fg.GlobalAttributeFamilyId = f.GlobalAttributeFamilyId
AND fg.GlobalAttributeGroupId = g.GlobalAttributeGroupId
LEFT JOIN dbo.ZnodeGlobalGroupEntityMapper AS ge
ON ge.GlobalAttributeGroupId = g.GlobalAttributeGroupId
AND ge.GlobalEntityId = e.GlobalEntityId
WHERE e.EntityName = N'Store' AND e.IsActive = 1
AND a.AttributeCode = @AttributeCode;Repair only the missing edge you own
Compare the intended path with a known working Store global attribute of the same type. A null group ID means the intended group was not found. A group ID with a null attribute/group mapper ID means the group exists but the attribute is not associated with it. Apply the same distinction to family and entity mappings.
If the definition belongs to a different entity or has an incompatible type, stop. A blind mapping insert will not correct that design. Add a reviewed forward migration with entity-scoped lookups, duplicate checks, and preserved administrator values; the Store SQL migration recipe provides a bounded example.
Verify the Store editor and value read
Open the intended Store configuration in Admin, locate the field, save a fictional support label, and reopen it in the same locale. Read the value through the supported Store global-attribute application path. Check that an unrelated Store value and localized label remain unchanged.
For a Store setting, save one synthetic value in the intended Admin form and read it through the Store attribute service used by the consuming application. A product publish is unrelated: product attributes belong to PIM and require their own family, value, and published-product checks. Record the selected Store, locale, group, family, saved value, and application readback in the change record.
References and further reading
Bring your next engineering question.
Need a Store configuration extension reviewed?
Independent guidance from GCG. Znode is a trademark of its owner. Examples use fictional data and are not official platform documentation. Suggest a correction.