Are there any plans to separate default values from conditions? Currently you can set a Model’s fields default values with conditions, but there may be times when you want to apply conditions so that a query returns a set of records that match criteria, but you want fields on those records to get a default value that the field doesn’t already have, and therefore can’t be added as a condition as it’d mean records may not be returned.
There are ways around this of course, but I think separating the two functions out will help make it clearer as to the responsibilities of each.
Gary this is a great idea, I’ve wanted this as well for a long time. While it eventually makes starts to make sense that Conditions become default values on new records, it’s not immediately intuitive, and plus, there’s exactly the use case you’re describing, where you’d like Conditions that are NOT used as Default Values.
