Project:
| View Revisions: Issue #29310 | [ Back to Issue ] | ||
| Summary | 0029310: Ordering the grid by a field with multiple identifiers can be confusing sometimes | ||
| Revision | 2015-03-17 10:31 by caristu | ||
| Description | Ordering the grid by a field with multiple identifiers can be confusing sometimes. If the table has as identifier a reference for another table that also has several identifiers, and one of these identifiers is also a foreign key the sorting is done by this column, which is confusing for the users as the ordering criteria is not using any of the displayed values for the record. An example can be, having a view with two identifiers: - quantity - ma_wrphase_id At the same time, ma_wrphase table has these identifiers: - ma_work_requirement_id - ma_process_id - seqno In this case, the application takes the ma_work_requirement_id as the column used for the ordering (see the attached query). |
||
| Revision | 2015-03-17 10:29 by caristu | ||
| Description | Ordering the grid by a field with multiple identifiers can be confusing sometimes. If the table has as identifier a reference for another table that also has several identifiers, the sorting is done by the reference table id, which is confusing for the users as the ordering criteria is not using any of the displayed values for the record. An example can be, having a view with two identifiers: - quantity - ma_wrphase_id At the same time, ma_wrphase table has these identifiers: - ma_work_requirement_id - ma_process_id - seqno In this case, the application takes the ma_work_requirement_id as the column used for the ordering (see the attached query). |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |