Record Type / Editable Grid which one is better when we have 100 Columns.

I need to build an interface with 100 Editable Columns and all the columns need to be searchable & editable.
(Like a table with 100 columns and we should be able to input something and search / modify the data and submit to DB).
Which approach is suitable for this requirement? Should i go with Record Type / Editable Grid.
(I am aware that the performance may be slow due to 100 columns. But business want to evaluate how it looks like and see the performance)

  Discussion posts and replies are publicly visible

  • Hello ,

    Record Type should be a better option here where you can display the most relevant fields on the grid and after user selection, show an interface with all the 100 fields to update.  Also, Appian records are optimized and performance efficient with 1,000,000 records synced in the data server from (v  21.4).

    Having 100 columns in an editable grid means horizontal scrolling which is not a good user experience. 

    Regards,

    Ricky

  • I would strongly recommend you re-think this user experience. It sounds like you're wanting to replicate the UX of an Excel spreadsheet. But this is only ONE solution option to the real requirements you have. I would encourage you to derive the real requirements (WHAT is required, not HOW) and then device what solution options you have to meet those requirements. For example: a wizard (a series of user interfaces that logically lead you through a data-capture process) may be a better experience.

  • 0
    Certified Senior Developer

    Hi prasdar, I am with the others.

    Try to sperate your features.

    • When and why do you want to show data?
    • When do you want to modify a column? 
    • Is a record sufficient?  
  • Hi prasadr,

    In Editable Grid, you cannot display more than 20 columns (depends on the type of fields, the number might slightly vary).

    The horizontal scroll also doesn't work for 100 columns. The fields will be crunched in the display.

    You need to go with Record, prioritizing the fields to be displayed in the List View and capture all the fields in the form mapped to the Related Action.

    This way only on e record is exposed for editing. This ensures data security and  performance.

    Regards,

    Farnaz