Skip to main content
Question

Shopify Import Mapping to custom field

  • January 30, 2026
  • 4 replies
  • 14 views

S1AW
Freshman II
Forum|alt.badge.img

We have a custom UDF called UsrOrderSource that helps us track various origin sources for our orders. Using the Shopify integration, it would be ideal to map a parameterized value (eg Connector name - Store name, or in this case, ‘Shopify-Store443Austin’ ) to that UDF.

On the Shopify Import Mapping screen, I can select various order header level fields; but I cannot select my custom UDF. Why is this, since the UDF is part of the SOOrder DAC?

Ideally, map to a SOOrder UDF

This is one of those things where I am hoping I just haven’t gotten the mapping right- it seems to me like it would be SUCH a useful way to allow the low-code/no-code style to apply here.

I do see elsewhere that a customization was recommended for something else; do we really need a developer to have a UDF included in the mappings? :(

 

4 replies

S1AW
Freshman II
Forum|alt.badge.img
  • Author
  • Freshman II
  • January 30, 2026

I should add that it looks like we can map to an Attribute by using Sales Order → Advanced from the ERP Object picker; but I don’t see the UDF in the picker. This is also confusing to me because the Attribute is stored in CSAnswers where the Usr field is stored in the SOOrder DAC. So if anyone has intuition on this and can explain, I would be interested to learn about why it is this way. Thank you!


meagan59
Varsity I
Forum|alt.badge.img
  • January 30, 2026

@S1AW I believe all custom attributes / UDFs are available under the ERP Object “Sale Order → Advanced” list in the Entities mapping.

 


meagan59
Varsity I
Forum|alt.badge.img
  • January 30, 2026

I just saw your recent comment. Yes, you are correct. It may be that the field added by a customization needs to be added to the Entities options as well. Whereas, attributes show up automatically under ‘Advanced’.


S1AW
Freshman II
Forum|alt.badge.img
  • Author
  • Freshman II
  • January 30, 2026

@meagan59  thank you for responding! Yes I did make my way to the attributes; that would be a workaround for us, and perhaps what we need to do that- create the field as an attribute rather than as a UDF. I just find it confusing that the UDF isn’t showing up given that it’s on the same DAC.