This is how initially rendered.After fix and unfix it changes the sequence of columns at level 0 under individual group header.
I am using igTreeGrid for this. I do not know what version we are using. Can someone guide me how to check the version too. Appreciate help and positivity.
Thanks,
Shweta
Hello Shweta,
After conducting a thorough investigation and attempting to reproduce this exact behavior you described, what I can suggest is ensuring that each column in your grid configuration has a unique value for its key option.
Column fixing requires unique keys for each column to manage complex structures effectively. When columns share key values, it can lead to unexpected behaviors where the system fails to correctly bind data, disrupting the flow of the chart.
Since your implementation is undisclosed, I am attaching a sample for your reference. Please test it on your side and let me know how it behaves. If this is not an accurate demonstration of what you are trying to achieve, please feel free to modify it and send it back to me along with steps to reproduce. Alternatively, if the behavior cannot be replicated, please feel free to provide your own sample. Remove any external dependencies and code that is not directly related to the issue, zip it and attach it in this case.
Having a working sample on my side, which I can debug, is going to be very helpful in finding the root cause of this behavior.
To check the version of your igTreeGrid or any other component you can simply write in the browser JavaScript console $.ui.<widget_name>.version. For example $.ui.igTreeGrid.version. I have also added an implementation of this in the attached file for you to check out.
Thank you for your cooperation.
Looking forward to hearing from you.
Regards,
Arkan Ahmedov,
Infragistics
8507.index.zip
Thanks Arkan for the reply.Pardon me for repeated post. But on my side when I was submitting the post, the submit button kept showing that loading gif and that gave me the feeling that my post didn't go through. So I created it again. Sorry about that.
Virsion that I am using is '16.1.20161.1009'. I do have unique column keys for each columns. I will check your sample to see what I have done differently.In the mean time I am attaching brief code for my implementation to give you an idea.
igTreeGrid.zipThanks,
Thank you for sending over the sample to investigate the issue regarding the swapping of child columns after fixing and unfixing a column within your igTreeGrid.
I have thoroughly reviewed the sample you provided and I also made sure to downgrade to version 16.1.20161. However, I was unable to reproduce the swapping behavior you described. To assist further in identifying the discrepancy, I am sending back the configuration as set up in my environment, which appears to behave as expected.
Additionally, I have attached a link for a video that should provide a clear visual reference of the procedures followed and the resulting behavior observed during my testing phase.Link: treeGridFixUnfixV2
It's possible that a small difference in our environments or configurations might be influencing the results.
Could you please try this on your side and let me know if you observe any differences? If the issue persists, it would be helpful to understand any specific conditions or configurations that may not have been captured in the original sample.
Your feedback is crucial in helping us pinpoint the root cause and ensure a resolution. Looking forward to your response.
Best Regards,
treeGridFixUnfix.zip
Hello Arkan,
Thank you for your efforts for investigating this.
<!-- Ignite UI Required Combined JavaScript Files --> <script src="https://cdn-na.infragistics.com/igniteui/2016.1/z2yulzj/1009/js/infragistics.core.js"></script> <script src="https://cdn-na.infragistics.com/igniteui/2016.1/z2yulzj/1009/js/infragistics.lob.js"></script> <script src="https://cdn-na.infragistics.com/igniteui/2016.1/z2yulzj/1009/js/infragistics.dv.js"></script>
I am glad to hear that we have pinpointed the root of the issue. I would definitely recommend upgrading to version 2016.1/latest as it resolves the problem. There should not be any breaking changes between the specified versions.
For detailed information about what each version entails, please refer to the 2016.1 and 2016.2 Release Notes. Additionally, in the Help Topics of Ignite UI for jQuery, each volume release is well-documented and provides information about its breaking changes. It is also advisable to familiarize yourself with the product’s lifecycle and support guidelines available on our website.
If you need further assistance or have more questions, feel free to reach out.
Best regards,