We are using the Tulip API extensively to pull data from the platform into other tools. One pain point we have found is the keys dont dynamically change even if columns are renamed. The keys follow the format below:
[unique 6 charcter identifier] _ [column name with spaces replaced by ‘_’ ]
The issue is when the column name is updated, this key doesnt change. I could see keeping that identifier as the source of truth for the field (much like how IDs are immutable), but there is no reason that the second half cant dynamically change.
What this would allow is the software we are using to talk to the API to either:
- reference the immutable part of the key so table changes dont break the logic
- Reference the part that changes, but it would actually reflect what the field contains
Currently we are stuck with a lookup table of essencially:
This mapping is completely manual and presents a massive risk of runtime errors that are hard to catch.