We can’t rename Smart Fields because the name is being used in export definitions not the GUID. When queries are used in selections the GUID is used which means when we change the name of the query it changes the name of the query within the selection.
In 2.9 – Export definitions used the query names and smart field names. When we changed the query name or smart field name it broke the export definition. We had to create new export definitions.
This was partially fixed in 4.0. The export definition looks at the GUID for the query but still looks at the name for the smart field.
Thanks, Pat.
Jessie - this idea remains open for voting. No other updates.
Any progress on this one?
We can’t rename Smart Fields because the name is being used in export definitions not the GUID. When queries are used in selections the GUID is used which means when we change the name of the query it changes the name of the query within the selection.
In 2.9 – Export definitions used the query names and smart field names. When we changed the query name or smart field name it broke the export definition. We had to create new export definitions.
This was partially fixed in 4.0. The export definition looks at the GUID for the query but still looks at the name for the smart field.