I am kind of confused about what it means, the new and old…
Does it mean the newly created fields do not make the distinction and they will be always set to default value regardless how the record is created?
I am kind of confused about what it means, the new and old…
Does it mean the newly created fields do not make the distinction and they will be always set to default value regardless how the record is created?
I reported all 4 of those scenarios to them as a major inconsistency bug last year — I’m glad to see that they have finally made default values consistent across all methods of creating a new record!
I noticed this improvement sometime during this year — it looks like January 31, 2024 was the date of the improvement.
Very interesting that they distinguish between old fields and new fields to not disrupt people’s old workflows.
They say they want to focus on bigger customers which means fix carefully and thoroughly and don’t disturb if it’s ain’t broken.