Tying OptionSet descriptions to CRM is incredibly difficult due to the column renaming that fivetran does in the destination. 

Mapping the values of stringmap to crm entities programmatically is impossible due to the column rename rules performed by fivetran before being put into the destination. 

For example, the Contact entity in CRM has a field named "address1_addresstypecode" which contains an integer. This attribute has a corresponding value in the stringmap table so we can get the string description of the type code "Primary" vs. "Bill To". However, when fivetran syncs the table over to snowflake, the column "address1_addresstypecode" gets renamed to "ADDRESS_1_ADDRESSTYPECODE" this renaming makes tying back to the table much more difficult. 

There are two possible fixes here: 

1. Have the connector itself pull the string description value for the type code (easiest for users)

2. Include an additional column in the STRINGMAP table that has the destination column name along with the attribute name so we can programmatically pull descriptions rather than manually having to define each.