Submitted by gregory on 2009/08/13 04:42
In order to prioritise work, I sort items on Itemmodified desc.
 
However, I must somewhere have a rule established which is automatically updating all Items and in the process resetting Itemmodified. This occurs infrequently but of course messes up my prioritised list.
 
Would it be possible and desirable only to update this field if an item was "explicitly" changed? (And no, I'm not exactly certain what I mean by explicitly; perhaps from the keyboard?)
 
Comments and clarifications would be welcome!
 
Mark

Comments

I think you'll have better luck creating your own date field, sorting on it, and tying it to ItemModified conditionally. If your "explicit" changes to an item always include updating the field named "Item", but your rules do not, then you can add an auto-update equation to the Item field:

AM: MarksDate=[ItemModified]
 
Indeed, you can put that same trigger in any or all of the fields you update solely and actively by keyboard.

("Item" is not a great name for that field, btw, as it's almost a keyword. ItemBody would be better, but it's probably too late to change at this point.)

Jerome

gregory

2009/08/13 09:46

Permalink

Hmmm... I'm still thinking about this one.
 
"
I think you'll have better luck creating your own date field, sorting on it, and tying it to ItemModified conditionally. If your "explicit" changes to an item always include updating the field named "Item", but your rules do not, then you can add an auto-update equation to the Item field:

AM: MarksDate=[ItemModified]
 
Indeed, you can put that same trigger in any or all of the fields you update solely and actively by keyboard.

("Item" is not a great name for that field, btw, as it's almost a keyword. ItemBody would be better, but it's probably too late to change at this point.)

Jerome
"
 
Item is used in almost all my grids. It's also a system field. I'm not in fact certain what I did (on 11th August) which changed ItemModified on all my existing Items!
 
Of course I could make a ModifiedDate field. (I already have a CreatedDate field which retains the date on which I created items imported from my (very ancient) Ecco file.) Then, if I always applied a form to changed items which included ModifiedDate, all would be well.
 
It's just that the approach is not quite fool-proof. And I know myself too well to believe that I won't at some point foolishly forget to change my ModifiedDate.
 
Mark Gregory, Rennes, France - GMT +1/+2; EST +6