Dear,
I have found a bug which exists for a long time.
Steps to reproduce:
1) Create master detail grid (let's name it "A")
2) In "details" use another igx-grid (let's name it "B)
3) Create B grid, using igx-column tag
Effect:
When you open any row from grid master ("A"), columns from detail grid will be copied to master grid.
I made this modification with example from infragistics doc.
You can check this bug here:
https://stackblitz.com/edit/angular-8rkghx-octa9h
Of course, I could get rid of this bug, but sometimes you want to use 'igx-column' tag and you cant.
Hello Dram,
Thank you for contacting Infragistics Community!
The issue you’re talking about is listed as a known limitation in the Master-Detail Grid topic in our official documentation. As stated there, this limitation can be avoided using autoGenerate=true for the nested grid. In case some aspect of those columns need to be modfied the onColumnInit event can be used.
Please let me know if you have any further questions.
Thank you for using Infragistics Components!
Best Regards, Martin Evtimov Entry Level Software Developer Infragistics, Inc.
Are there any plans on the horizon for addressing this? I have tried using the onColumnInit event, but it makes all of the parent grid's columns disappear.
If we can't resolve this issue, we are going to have to purchase and implement another angular grid.
Hello Karl,
Thank you for getting back to me!
I have updated the provided sample so that it is using cell and cellEditor templates. The purpose of this sample is to demonstrate that using the columnInit event both templates (igxCell, igxCellEditor) and pretty much any possible configurations to the igxColumns can be assigned.
In case you decide to stick to the igxGrid please let me know if I may be of any further assistance.
Best Regards, Martin Evtimov Associate Software Developer Infragistics, Inc.
Thank you for the sample. Unfortunately our grid definition is quite complex (frozen columns, grid columns dynamically served from the server side) and heavily reliant on templates, so I am not sure where exactly the breakdown happened.
And primarily because of the heavy reliance on templating, I don't think that we could (or would want to) try to build the column definitions in the oncolumninit method. So for now, we have selected a different vendor to provide this grid functionality.
Thank you for contacting Infragistics Support!
I believe you will find the following sample I have prepared for your very helpful. As you can observe using the columnInit event I hide some of the columns of the nested grid and still the parent grid’s columns are persisting.
If this sample is not an accurate demonstration of what you are trying to achieve please feel free to modify it and send it back to me for further investigation.
Looking forward to hearing from you.