row number in list

usr338

Hi, i think another (my be easy) improvement that can be made on list field is the showing row number.
I mean a row number that is not attached (or related) to records. just showing current row number of any record in list.
I know , it is possible to use sub query to do that , but it cause extra query to be run for each row.(and it only show correct row number if list sort does not change)

gabriel

Please understand that every little feature we add, increases complexity - the UI needs additional components, we need to consider row numbering on all future changes, deal with list layout issues if there is another column that is always/sometimes there (depending on implementation), decide how to offer that option (is it part of the app schema? should a user be able to overwrite? should it always be optional?), etc.

Do you have a strong case on why you need this feature?

usr338

gabriel Dear Gabriel , deciding on what feature should be included in platform, completely depends on you and your team. (obvious 😉)
I don't know how R3 is implemented, I thought having row number in list, is something that is not dependency on data that list shows.(every number is rendered can have row number beside) and it can be optional. i thought may be like header and footer it can be part of list structure and can be optional to be visible or not. (and may be can be done with low effort).
Actually it is useful when using list to show reports and export to CSV.(small ones)
And yes, i know, as we discussed before , using external tools is the best approach to create reports. TNX

gabriel

Adding row numbering to list fields would not automatically make them available in CSV exports. These are 2 components that work very differently. In order to offer both, we´d have to put in the work to implement this feature in the list component as well as the server-side CSV-exporter.

I´ll add it to the wish list, but I don´t see a strong case yet, why this feature is particularly useful.

Using external tools is not "the best approach" to create reports, I would say. Organizations run reports inside r3 every day, including nice-looking PDFs. It can be an easier approach, depending on what you want to achieve and what tools and/or skills you have.

usr338

gabriel @Thank you and here are small list of case that row number can be helpful :

Reference for large data table and ease of collaboration :example: "can you double-check the data in row 18?"
Pagination and scrolling context: row numbers can provide users with context when navigating through paginated lists or scrolling down long tables. It shows their position in the overall dataset.
Selection and bulk operations : when selecting multiple rows for actions (e.g, deleting, exporting), row numbers simplify describing or confirming which rows were selected.( and in R3 we don't have selected items for now)
Debugging and error identification
Tracking sorted or filtered data: example: after sorting by Date, "this item is now in row 4"
Data entry validation (In future when R3 has Inline edit capability) :example :"row 5 has an invalid email address."
and may be more..

To be honest, none of them are strong case in my application, except in reporting.

gabriel

Thank you for providing these points. I´ve added them to the feature proposal.