Five column limit on Items table?

[Jev Björsell]

There appears that the Items table that appears on a PO or SO is limited to displaying only five columns. 

Can someone explain the technical reasons of why this is so? Hopefully we can discuss how we can improve on this situation. Five columns is really too little for us. 

For our needs, we really need Item Code, Item Name, Required Date, Description, Qty, Unit Price (import_rate), Sub Total. If you add in the line number, then that is 8 columns.

-Jev

[Aditya Duggal]

Hi Jev,

I am with you on this issue, the 5 column limit in the child tables is too low, but I guess it has been entered so as to avoid the horizontal scroll bars which were difficult to deal with in touch based devices like ipad etc.

Even I would be looking for an amicable solution to this problem where the  column nos can be increased without disrupting the usage on mobile devices.

[lxnow]

 I think that the 5 column limitation is unnecessary and that it is a quick-fix limitation to ensure a consistent UI experience..  If sys admins see that the table is already too cluttered with too many columns, then it is his/her responsibility to reduce the # of columns. 

[Jev Björsell]

Could we switch the items table to be an actual HTML table and use the .table-condensed bootstrap table size? 

The five column limit is really killing us, can we please get this limit raised for version 4.0?

Thanks,

-Jev

[Anand Doshi]

Hi Jev,

Table doesn’t seem to be a good option, given the row editor widget.

What we can do is show the first 5 fields in column layout and show the rest of the fields below as two col responsive layout:

Sr   Column 1    Column 2    Column 3    Column 4    Column 5

1    Value 1     Value 2     Value 3     Value 4     Value 5

     Field Label: Field Value    Field Label: Field Value
     Field Lable: Field Value    Field Label: Field Value

——

2    Value 1     Value 2     Value 3     Value 4     Value 5

     Field Label: Field Value    Field Label: Field Value
     Field Lable: Field Value    Field Label: Field Value

.
.
.

The row height will increase, but it will also keep the design responsive. What do you say?

> --
> Note:
>
> If you are posting an issue,
> 1. We should be able to replicate it at our end. So please give us
> as much information as you can. Please see it from the point of
> view of the person receiving the communication.
> 2. Paste your code at http://pastebin.com or http://gist.github.com
> and send only the URL via email
> 3. For sending images, use http://imgur.com or other similar
> services. Do not send images as attachments. Links are good.
> Same goes for any file you are going to send.
>
> End of Note
> ---
> You received this message because you are subscribed to the Google
> Groups "ERPNext Developer Forum" group.
> To unsubscribe from this group and stop receiving emails from
> it, send an email to erpnext-developer...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

[Aditya Duggal]

Hi Anand,

I think this would be a good thing since as rightly pointed out 5 column limit is a big limitation, I agree that we cannot go back to the tabular form since that creates a lot of problem for mobile devices data entry and this responsive layout is much better than that and I guess that the suggested thing would remove a lot of problems of that limitation.

[Anand Doshi]

Added an issue in Framework: https://github.com/webnotes/wnframework/issues/423

Thanks,

Anand.