Hi Nguyen,

Thank you for posting to Infragistics Community!

It appears that the sample you have shared is not runnable and is using a very outdated version of both Angular and Ignite UI for Angular. The currently supported versions are 14.2.x and 15.1.x, with 16.x to be released very soon. Moreover, the error from the screenshot does not seem to reference the Ignite UI library code.

Although, from the template code in the shared sample I can see that it demonstrates displaying a dynamic collections of columns with the help of the *ngFor directive as well as conditional cell templates.

So, I can recommend checking out the following topics from our documentation on the subject:

• Angular Grid Column Configuration
• Cell Template
• Cell Editing Template

Additionally, here is a functioning sample against version 15 demonstrating the same. You can use it for reference in implementing the target features in the grid, such as cell editing.

If the sample and the provided resources are not an accurate demonstration of what you are trying to achieve, please, fork and modify the StackBlitz demo with only the relevant code and send it back to me along with more details, so I can assist you further.

Best regards,
Bozhidara Pachilova
Associate Software Developer

cond.zip

The file above contains the code I'm using.

<igx-grid [hideRowSelectors]="true" #grid1 [data]="rowData" [height]="null" primaryKey="title" displayDensity="compact" [clipboardOptions]="copyOptions" paste-handler
          (onDataProcessed)="dataPasted($event, grid1, 1)"
          (cellEditExit)="cellEditExit($event, 1)"
          (gridKeydown)="customKeydown($event, grid1)"
          (keydown)="handleKeyDownBoardEvent($event, grid1)"
          (keyup)="handleKeyUpBoardEvent($event, grid1)"
          (cellEditEnter)="cellEditEnter($event, rowData)"
          (cellClick)="checkClickFluidType($event)"
          (selected)="setCellSelection($event, grid1, 'onSelection')"
          (rangeSelected)="setCellSelection($event, grid1, 'onRangeSelection')"
          (activeNodeChange)="onActiveNodeChange($event, grid1)"
>
  <igx-column field="title" header="項目名" [width]="widthTitle" [pinned]="true" [headerClasses]="'text-center'" [cellClasses]="cellCls2">
  </igx-column>
  <igx-column *ngFor="let c of columns" [field]="'no'+c" [header]="'No.'+c" [width]="'130px'" [editable]="true" [headerClasses]="'text-center pd0'" [cellClasses]="cellClsDirtyCheck"></igx-column>
</igx-grid>

  addTab() {
    this.columns.push(this.columns.length + 1);
    this.rowData.map(row => {
      if (row.field === 'WITH_FIN_A' || row.field === 'WITH_FIN_B') {
        return row['no'+this.columns.length] = true;
      } else {
        return row['no'+this.columns.length] = '';
      }
    };
  }

related html and ts files.

First I have column number from no1->no16.

When I click "追加" button (add column) it generates no17.

Here I click to edit the data of column no17, I am getting the above error.

Note: Column no17 is being generated by the library after I push to add an element to the columns array.

So, I have modified a fork of the previously referenced StackBlitz to dynamically add columns to the grid, similar to your app.

In the isolated app, no errors are encountered and the newly added columns’ cells can be edited.

From the provided template files (cond.component.html, line 76), I can see that the cell templates contain complex markup, including an html table. Generally, this would not be quite advisable, as the cells’ purpose is to display data as simple as possible, and nesting tables within grid cells would not be considered the best layout.

Now, I cannot really test this for the reasons mentioned above, however, I can also see the cellEditEnter and cell click events are handled for the grid. Since they are directly related to entering cell edit mode, and I can see they contain some complex application logic (cond.component.ts, line 284, line 371), it is very likely that the errors are related to this functionality. The call stack does not indicate any Ignite UI for Angular code, so my suggestion is to check the code files and lines indicated by it, put some breakpoints and go deeper through the call stack via the Developer Tools in order to debug the source of the error.

Please, note that since the isolated sample does not demonstrate a similar issue, this indicates it is rooted in the application level and has to be investigated and handled on the same as well.

Since our policy involves working with isolated samples, I would still suggest forking and modifying the StackBlitz with only the relevant code and see if the issue can be reproduced there. Thank you for your cooperation.

Best regards,
Bozhidara Pachilova
Associate Software Developer

One thing I noticed is that it seems the error is not reproduced when I uncomment the custom cell edit template – check it out again on the same link. So, what I can suggest for now is defining a custom cell edit template as in the sample as a workaround.

I will be looking into this matter and will update you once I have more information

Best regards,
Bozhidara Pachilova

After further investigation, I have logged this behavior in our GitHub repository and you can view the issue here. 

In order to receive a notification whenever a new information is available, please make sure that you are subscribed to the issue. This can be achieved via “Subscribe” button.

Please let me know if you need any further assistance regarding this matter.

Best regards,
Bozhidara Pachilova