In some very obscure cases I'm seeing that CellControlAttached is not fired correctly from "xamgrid" after data-binding (for bound columns).
The problem only seems to happen the SECOND time that the underlying item data is re-populated from a data source. On the FIRST time and all other times after the SECOND time, the event is fired. Also the problem doesn't happen on my developer workstation, but it happens consistently in our Citrix deployment environments.
This issue has come up at other times in these forums, and it seems like an ongoing problem that infragistics hasn't totally pinned down. Is there a consistent workaround? I found a workaround that is really, really ugly which is to call XamGrid.InvalidateData twice, (and the second one happening via the Dispatcher). Any other ideas would be welcome, especially ideas that are less ugly than mine.
I realize that the XamGrid is on its way to deprecation but I'd like to get a bit more life out of our existing code. Some of it was written fairly recently (before we were told about the IG roadmap for xamgrid).
We are currently running 17.2. If there is another volume that is more stable for this control, I'm eager to try another.
Hello ,
Thank you for the update.
Looking into our internal bug tracking system, I noticed a couple of bugs been logged for CellControlAttached event and been fixed for 17.1 and up.
May I know which V17.2 build you are using? The latest is 20172.2188. if you dnt have the latest, please update it to 2188 and test if it resolved the issue or not.
Looking forward to hear you back.
Sincerely,Divya JainAssociate Software Developer
These are instances in your service releases that indicate the same issue:
* CellControlAttached event is not fired correctly when the grid is bound to hierarchical data.* CellControlAttached event is not raised for every cell when having SparklineColumn * CellControlAttached event is not fired for the first cell of a row when having Group columns.
For example, it happened in this forum question as well:
https://es.infragistics.com/community/forums/f/retired-products-and-controls/55200/possible-bug-cellcontrolattached-is-not-always-fired
I also saw a reference to a related bug being fixed in one of your service releases. It had said there were special scenarios where the event (CellControlAttached) wouldn't fire).
Can you give me ideas about how I might troubleshoot the firing of that event, if the problem only happens in Citrix?
Also I was going to try to workaround the related issues by disabling virtualization but there doesn't seem to be a way. Is that true? Is there a mode of operation where the xamgrid will regenerate cell controls, (and thereafter unconditionally run the "cellcontrolattached" events). Is this what happens when you run "InvalidateData" on the xamgrid?
Hello David ,
Thank you for contacting.
I understand that the issue is not happening in the development environment but it does on Citrix deployment environments.
Can you isolate the issue with some other event and behavior ,and provide us the sample for further investigation.
As you mentioned that this issue came up the second time on the forum, could you provide us the link of the first time post to get more information about the issue and provided workaround.
Looking forward to hear you back. Sincerely,Divya JainAssociate Software Developer