Hi,
sometimes we refactor Apps and replace a manual field with a calculated field.
Problems:
- I don’t know, where the current field is in use (calculation, automation etc.) - generic problem, even when I want to do some clean up with meanwhile unnecessary fields. I just don’t know and its difficult to investigate.
- I can’t change an existing field (e.g. category field) into a calculation field (which results into the same values as before and potentially doesn’t cause any interruption for other calculations or automations.
- I doubt, that adding a new field and adjusting the external_id (Great! 🆕 Update external IDs in App Developer Info) of the field will not solve it for this, as I guess for calculations and automations the internal unique ID is used?
Thus - if there is no smarter way, I would like to get the ability to change any field into a calculation field. 