To convince users to move from Excel is very painful, because adding/entering data is so slow. We have approx. 25 columns in both grid and BOM tab. First, there is no on-edit trigger – we have data integrity problems because users forget to run an on demand script that handles our calculations. To give an example of expectations, a quick Google finds an example JavaScript widget: https://handsontable.com/examples?manual-resize&manual-move&conditional-formatting&context-menu&filters&dropdown-menu&headers The display performance is excellent The grid has a clean feel, with less wasted whitespace. Faint grid lines help visibility Moving around is natural (tab to cell, cursor keys, …) The columns filter in a familiar Excel-type way Drill down (multi-column filtering) in familiar Excel-type way Numeric columns are correctly aligned (eg right for numbers) Display of data is localised to browser settings (decimal points, etc) Columns are color-coded red/green for negative results Selecting ranges, and copy/paste from Excel works naturally Ability to freeze columns so when entering data on right side, I am sure what I am editing Export directly to CSV Nested headers Collapsible columns to hide very wide data Ability to hide columns when working Copy down functionality Cell level validations Different permissions for columns (like section permissions on item details page) … Please play with the example above to give an idea of what users are expecting from a grid widget in a webpage. To help acceptability of our FLC-based solution, we request consideration to a re-implementation of the FLC Grid widget, and on edit trigger for other tabs. Thank you Maarten.
Show More