Tracked back through the versions if that might perhaps help some.

Worked in version 10.2

Stopped working in Version 10.3.

Nick

Will look forward to your results or a better workaround.  It's not going to be a simple task to recode everything as you suggest because these are all built dynamically on the fly for a couple hundred grids or so.

Thanks

Nick

Hi Nick,

This is a very odd bug. I don't see why adding the ValueList into a ValueListsCollection is having an effect here. My best guess is that being in a collection is preventing the grid from cloning the ValueList - but that should not be the case.

May I ask why you are using a ValueListsCollection? It's kind've strange to use a separate ValueListsCollection outside of the grid and then pass in the grid's Appearances collection to it. If you want to store the ValueList in a collection, then it would be better to simply use the existing ValueLists collection on the grid.DisplayLayout. This collection is already hooked up to the Appearances collection on the DisplayLayout.

Just FYI, the only reason the ValueListsCollection requires you to pass in the Appearances is so that the ValueLists and the ValueListItems can reference an Appearance by key. So unless your ValueLists are actually referencing the Key of an appearance instead of the Appearance object itself directly, this is unnecessary.

Now that, in itself, probably doesn't help you, but if you are not directly using the keys of the Appearances, then you might be able to work around this issue more easily by simply replacing ValueListCollection with List<ValueList>.

Hey Mike,

Long time since I've had a problem, knock on wood, and it seems very odd to me also.  Yes I can imagine you are wondering why in the world do it this way.  Nothing to do with appearances I only did that to make the debug of this issue as simple as possible.  Actually we have an array of valuelistcollections with one level for each band and the valuelists are all retrieved using stored procedures all at once into the collections.  When the grid is created the appropriate lists are assigned to the columns.  The grids are built dynamically.  Yes perhaps I could use the Valuelists collection on the grid and that may be the option needed.  Seems there was some reason not too when I was doing the design back in 2003.  Vaguely remember something about assigning value lists to different grids giving a appearance bug but I haven't crossed swords with that one in years.

Hope you have been doing well and everyone is appreciating your superior help over all these years.

Thanks,

Nick

Hi Nick,

Maybe you did it this way so that you could keep separate collections of ValueLists for each band, rather than having all of the ValueLists in a single collection.

But either way, changing ValueListColection to List<ValueList>, or maybe Dictionary<string, ValueList> should be pretty easy to do with a minimum amount of code changes.

We will look into the bug, either way, but the workaround might be a good idea, anyway, and it will get you going sooner if this is a blocking issue.

Thank you guys for setting up the ticket.  Not a critical problem for me.  The users can generate reports via another interface I have written that dynamically generates RDL's for ReportViewer that handles most of the reporting grid's.  Appreciate all your help.

Nick

Hello ,

I just want to announce that this issue is fixed in Infragistics 11.1 service release 2042.

Thank you.