[Bug]-[1450]:Maintain order of data when the table's schema changes

[dilippitchika]

Is there an existing issue for this?

• I have searched the existing issues

Description

When i have defined a table schema with all the customisations necessary and then the schema of the table changes to have only a few columns from the original schema or no columns, the customisations I made are lost.

Steps To Reproduce

1. Add a table widget
2. Bind it to data
3. Customise the table schema like change the bg color in a column
4. Pass data where the column is not present
5. Now pass the data again where the column is present
6. Observe the customisations are lost now.

Public Sample App

No response

Version

Production

Front conversations

[dilippitchika]

@sbalaji1192 @keyurparalkar here's my thought expanding Nikhil's idea

If the column which was configured disappears and re-appears then we can check based on the widget's original dsl if the column configuration and order contain the column name. If it does then we can add the column back in the same column order and keep the schema config for column same.

The idea here is when the key is missing from table data we generate the table without the column, but if the key comes back we check if it was is in the original table dsl and show the column. I don't think there's any value in showing an empty column and we don't need user intervention here.

[dilippitchika]

Stats

Stat	Values
Reach	725
Effort (months)	0.5

[dilippitchika]

@rajatagrawal can you check this out?

[commandodev]

This looks like a good work option to me.

The worst of all worlds is if you make a mistake in binding data and the column disppears for ever. This is basically impossible to recover from and you have to revert your whole canvas change.

My usecase is where I have onSubmit handlers and custom names for a column and cross multiple different versions of a table. One mistake wiped out several columns and I had to create a branch, revert master and then try to recover bits of code from the branch I created. Cost me at least a couple of hours.