I noticed an issue regarding updating field API names and the use in Flows.
Any changes in API names are automatically 'refactored' in flow. i.e., assignments, use in decision elements and screens is updated as expected. Nothing wrong, great!
But when referencing the field at runtime (when running the interview) the field seems unaccessible, the flow returns an error like this:
UPSERT --- UPSERT FAILED --- ERRORS : (INVALID_FIELD_FOR_INSERT_UPDATE) Case: bad field names on insert/update call: *field api name* --- for SFDC record with ID : null
The first time this happened I spend considerable time trying to figure out how this is possible, only to find out that after 15 - 60 minutes the problem solved itself.
Does anyone know whether this is a known problem? Right now everytime I update a field API name working in Flow, I take a long coffee break.