Another thing I've noticed still is that during the creation of a record, date fields are still set to the current date. I really need to stop this behavior since I want to use a field to record when salesorders are fully invoiced (the date that this event first occurs). We use this for financial reporting so we need to be able to rely on this field. This is a custom field, where the generated type is already set to 2, as per this answer (to a question from Joe in 2006!).
Wait, this seems to be related to a workflow I use. The workflow is (on SalesOrders):
- Until the first time a condition is true
- field that is auto calculated by aggregating all related invoices should be 'greater than or equal to' the 'sum_nettotal' field
- Then field should be get_date('today')
I see in the workflow list that this workflow is listed before the 'Update financial fields on every save' workflow. I'll try and reverse their order to see what happens.
Wait, this seems to be related to a workflow I use. The workflow is (on SalesOrders):
- Until the first time a condition is true
- field that is auto calculated by aggregating all related invoices should be 'greater than or equal to' the 'sum_nettotal' field
- Then field should be get_date('today')
I see in the workflow list that this workflow is listed before the 'Update financial fields on every save' workflow. I'll try and reverse their order to see what happens.