Filter menu broken when undefined on data

Question

undefined values crashes menu filter - grid

Uncaught TypeError: Cannot read property '0' of undefined

at FlMenuOptrUI.dropSelectedVal

const data = [
  { _id: 1, firstname: undefined, lastname: "Doe" }, // undefined value will crash filter menu
  { _id: 2, firstname: "Mary", lastname: "Jane" }
];

example
https://codesandbox.io/s/modest-mcclintock-w2skw?file=/src/App.js

Sujith Kumar Rajkumar · Accepted Answer

Hi Dario, 

Greetings from Syncfusion support. 

If the first row contains undefined or null value for a column then column type needs to be defined for that since based on this initial row data only the column type will be set and based on the column type the filter menu will be rendered. This is the Grid’s default behavior. We have modified the provided sample based on this which you can find below, 

Sample: https://codesandbox.io/s/lucid-wing-htzei?file=/src/App.js 
 
Column type API: https://ej2.syncfusion.com/vue/documentation/api/grid/column/#type 

Please get back to us if you require any further assistance. 

Regards, 
Sujith R

Dario · Answer

i see, thanks!

Prasanna Kumar Viswanathan · Answer

Hi Dario, 
 
Thanks for the update. 
 
Please get back to us if you need any further assistance. 
 
Regards, 
Prasanna Kumar N.S.V

Julius Peter · Answer

Dear Syncfusion team,I would strongly recommend to change the grid filter standard behavior to better handle such a situation (happens probably quite often). If no type is specified on a column and the first entry is null,  default types (set for the whole grid, the installation or even in general) could be used. Would make life of a programmer using this component much easier ...... error messages like this are very difficult to trace and decrypt....RegardsJulius

Joseph Christ Nithin Issack · Answer

Hi Julius,  Greetings from Syncfusion support.

By
default, in EJ2 Grid, the actions like filter, sort, etc. will be performed
based on the type of the column. If the type of the column is not set, grid
will automatically assign the type based on the value in the first row of the
column. If the value of the first row of the column is null/undefined, the
column type will not be defined. So, if null or undefined value is present in
the initial row of a column and column type is not set for that column, then
the type will be set as ‘null’ which causes problem.   As you have mentioned, if we set the default type(e.g.,
string) for the columns when no type is specified on a column and the first-row
data is null, then the grid will consider this as a string column and perform
all the actions considering this as a string column. This may cause the grid to
show improper results when performing the actions like filtering, sorting etc.
This is the reason we have not set the default value for the column type.Regards,Joseph I.