Mapping PI Cycle Description Instead of ID to Shopify

just make sure you create a metafield in shopify as a text field and it should map without issue. 

Hi ​@kkeating24 , yes, the metafield already exists in Shopify, but the CycleID is synced. What we need is the Description.

One option we are considering is to create an attribute that will hold the Description. Using an Import scenario, we would populate this attribute according to the CycleID Description. Then a business event would update this attribute every time a PI Cycle is updated. That attribute would be mapped and synced to the Shopify metafield.

I am not sure if there is a more elegant solution than this.

OK, i think I understand.  So the description is not available as a field to ‘export’ in that list of values?  

Then yes it would need to be stored somewhere to access it, to then publish to a metafield. 

Sometimes you can actually get the Entity Mapping to use fields that are NOT in the list of values, but it takes some trial and error:

For instance you might be able to say ItemSettings.CycleID_description   or   ItemSettings.CycleID_descr

I tried ItemSettings.CycleID_description and ItemSettings.CycleID_descr, but both didn’t work. 

sounds like a custom field or an attribute.  Once you add an attribute it will show up in the list of values and you can map it to a metafield in shopify. 

Hi ​@jib87 were you able to find a solution? Thank you!