1. Home
  2. Forum
  3. React - EJ 2
  4. Checkbox selection column plus last column with template produces an error

Checkbox selection column plus last column with template produces an error

Hi,

please have a look at the following minimal example: https://stackblitz.com/edit/syncfusion-grid-issue-1?file=index.js

To reproduce the error, select a check box.

The error does not occurr under the following circumstances:

  • the selection column is removed
  • the "action" column is moved between the other two columns (i.e. it is no longer the last column)
  • the row selection events are not handled (i.e. no react state change on event).
Please verify.

Regards, Steffen

3 Replies 1 reply marked as answer
PG Praveenkumar Gajendiran Syncfusion Team July 1, 2021 08:01 AM UTC

Hi Steffen, 
Greetings from Syncfusion support.

We checked your provided information, based on that we would like to inform you that the reported problem occurs due to the template column does not have the field value, So we suggest you to provide a dummy value to the field value for the Template column to resolve your reported problem. 
This is demonstrated in the below code example, 
<ColumnDirective field="key1" headerText="actions" template={() => <span>dfshdf</span>} /> 

We have modified your sample based on this for your reference.

Sample: https://stackblitz.com/edit/syncfusion-grid-issue-1-pbrftc?file=index.js

Please get back to us if you need further assistance.

Regards,
Praveenkumar G  


Marked as answer
SH Steffen Harbich July 1, 2021 09:36 AM UTC

Ok, where can I find in documentation that "field" has to be specified and why doesn't grid complain when it's missing?

Unfortunately, there is another issue with grid that I cannot reproduce in a minimal example: After a react state change, grid doesn't rerender the rows, hence changes are not displayed. I had to implement another workaround to fix this: using "key" of component to make it recreate on changed data but this will forget state in grid like paging, sorting, selection etc.

Beside the issue, here is short general customer feedback: I was hoping that syncfusion upgrade from 18.2.x to 19.1.x was improving overall stability and fixing a lot of issues that occurred before. However, at least the same amount of issues fixed were also introduced in the new version. I wasted a lot of time on finding workarounds for the new issue. I wouldn't recommend using the framework at all and we consider migrating to another framework. The react principles are not respected as the components are not designed for react but for a general use.


Have a nice day,

Steffen


PG Praveenkumar Gajendiran Syncfusion Team July 2, 2021 10:58 AM UTC

Hi Steffen,

Thanks for your update. 
Query 1: “where can I find in documentation that "field" has to be specified and why doesn't grid complain when it's missing?”

Based on your suggestion, we have logged an internal documentation task for including the detail related to provide the field value for the Template column. We will update and refresh it online in any of our upcoming releases. We appreciate your patience until then.

Query2: “Unfortunately, there is another issue with grid that I cannot reproduce in a minimal example: After a react state change, grid doesn't rerender the rows, hence changes are not displayed. I had to implement another workaround to fix this: using "key" of component to make it recreate on changed data but this will forget state in grid like paging, sorting, selection etc.”

Based on your query, we could see that you have facing the “changes are not applied” issue at your end, So please share the following details to validate further on your query, 
  1. Complete Grid code example.
  2. Let us know the replication procedure to reproduce your reported case.
  3. Video demonstration to understand your reported issue better at our end.
  4. Please elaborate on your exact issue scenario with more details based on which we will check from our end and provide the further details.
Query3: “I was hoping that syncfusion upgrade from 18.2.x to 19.1.x was improving overall stability and fixing a lot of issues that occurred before.”

Based on your query, we understand that you have facing an issue when upgrading Syncfusion packages from 18.2.x to 19.1.x, please let us know what are the issues are you facing when upgrading Syncfusion packages from 18.2.x to 19.1.x based on which we will check from our end and provide the further details. 
Regards,
Praveenkumar G 


Loader.
Up arrow icon