Now that history data has its own data mapping for data migration, please use the same default value as the field itself has a default value.
So for example a mandatory checkbox field that has a default value of 0 in the col table: in the datamigration mapping it already inherits the default value value for itself. But the default value for the history data stays empty right now.
+12+12Note that we explicitly decided not to implement this, see Release Notes: 2026.1 | Thinkwise Documentation.
New mandatory columns and optional columns that became mandatory columns must have an explicit default value for the history data. The default value used for the main table is not applied to the history table, because it may not be valid to the history data. A validation has been added to alert you if this situation occurs.
Especially for Default expressions there are a few risks, as you might actually not want to set the value based on the current valid record, but instead on a value that was valid at a point in time.
For Default constant values we can definitely agree that defaulting it for history tables seems a good improvement indeed.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
