I inherited the Panorama system I work with over 15 years ago (when it was Pan 3). A very standard operation is to create a new customer record, from which invoices can be created. It initializes a field “CustomerSince” with today’s date at creation time. Another field “Updated” is initialized with today’s date when a new invoice is created for that customer. Doing this same operation in Pan X causes both “CustomerSince” and “Updated” with today’s date at creation time, which is getting a little ahead of ourselves (not everyone places an order at the same time their account is created).
I looked at the Design Sheet in Pan 6, and I find that the Default values for both fields are set to “today”. Except that in the “Updated” field it is spelled “tody” and it would appear that this field was originally set up to do that Default, but since it is spelled wrong it does not do that. And “not doing it” is the correct action, so I’ve never had occasion to explore this.
In the database converted to Pan X, the Default for “Updated” is also “tody” but it would appear that Pan X is “doing me a favor” by figuring out “what I really meant”. This is easy enough to correct, once I figured out where this rogue date is coming from, but it makes me wonder if I’ll find more unexpected “helpfulness” in my Pan X migration from 6. Can anyone shed light on this?