 dflaven
|
d9653c3e57
Preserve the initial sort order on lists by determining the default sort order of the tables based on the equivalence between the "friendlyname" and another actual field of the class.
|
9 years ago |
 romainq
|
b2618d03ae
Exports further improved:
|
9 years ago |
|
romainq
|
eaee9c5ddc
Exports: a fields spec can now be an extended attribute code (e.g. location_id->org_id->parent_id->code)
|
9 years ago |
|
romainq
|
8ddc97daa3
Export (all formats but XML):
|
9 years ago |
|
romainq
|
5501af41d0
Exports: support multi-column queries (e.g. SELECT l, p FROM Person AS p JOIN Location AS l ON p.location_id = l.id) with null values
|
9 years ago |
|
romainq
|
f6d23c2a56
Printable view: cosmetics on object names (hyperlinks) in the actual print view -reverse merging a file that was NOT ready for committing
|
9 years ago |
|
romainq
|
243d41a046
Printable view: cosmetics on object names (hyperlinks) in the actual print view
|
9 years ago |
|
romainq
|
e38eb53e3a
Export: for tabular exports, the label for the "friendly name" column must match the one recognized by CSV import (the very standard one, almost unused yet)
|
9 years ago |
|
dflaven
|
388bfea437
A little bit of polishing on the export feature to be ready for the beta.
|
10 years ago |
|
dflaven
|
47e596aa0b
Bulk Export redesign, addressing the tickets:
|
10 years ago |
