|
[
Permalink
| « Hide
]
David Peterson added a comment - 29/Jun/07 10:04 PM
I'm not sure what the best way to implement this is. Part of the issue is that rows can be reordered at whim, and it would be a pain to keep track of all the reorderings.
Now I have to remember the case for which I wanted this. I do recall thinking about that, and I would be willing to give up reordering for this item. In truth, there are several cases where I would like to forbid reordering.
Let me go find my use-case again, if I can't, I'll let you know so you can close this up. For some of my uses of table-data, it would be great to have an ID field, that could be use in reports, could not be changed by users and does not change when rows are re-ordered.
In one example, I have an action register implemented using table-data and each action has an ID which is specified by a number-data field. From this table, I generate an open actions table and a closed actions table. The ID's are used to refer to specific action, thus should never change for a particular action. Having the ID generated automatically, would just make things a little be cleaner and less error prone. I'm also trying to set up a template that includes an autonumbered table.
Ive tried using: {table-data:Summary|initialRows=3} || Description || | # {text-data:Summary|type=area|width=450px|height=5cm}<key point>{text-data}|{table-data} but the autonumbering resets at each line - Can anyone tell me if there is a way of continuing the sequence as each row is added? |
|||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Minor
Auto-increase for number-data in a table-data object