When using some of our list views our users are having issue where grid filters is stuck selected on their screen and are unable to turn it off.
The have their list view personalized not sure if that is the case as well. I have not deleted their personliations is see if that fixes it.
Just wondering if anyone else has seen this issue.
We just went live with 10.2.500.8 Today. From 10.2.300.9
Devin
Funny you should mention this. I just helped with an upgrade to 10.2.500.10 and the grid filters are stuck on as well. Did you report this to Epicor yet? If not, I will and I’ll share the case number with you.
no I have not reported this yet. Thanks for your help. Trying to see if the group saw it first and already had a fix
Just heard about it about 30 minutes before you posted. I’ll report it and let you know the Case.
Thanks Mark Your a gentleman and a scholar
That may or may not be but I’m unable to duplicate it on my system!!! I have a screen shot from a power user who I trust implicitly. He runs the classic shell but I still can’t replicate it. So I’m trying to find what is different between his system and mine. I may try to delete his personalization to see if that helps. One moment…
Baby steps. We migrated from a green screen system written in FORTRAN…
Okay I think it is a something to do with a personalization right now. As im not able to duplicate on my machine. I will try and remove that persons and see what it does.
all our users are using active home
The usual suspect in these instances is that a user “Saved Layouts” with the filter (also happens when sorting by columns in the grid).
Delete the personalization for the user; and then have them log out of Epicor and log back in - and it should go back to normal.
P.S. for those who customize screens - these things can get pulled into customizations as well; which can be a real challenge to remove from a customization without having to recreate it from scratch.
From what I can see. I have 2 users using receipt entry and it show up on their screen now.
This is definitely tied to personalization. It is reported under PRB0218737 in the Epicor support system and is scheduled to be looked at soon.
I have deleted the personalization and it has came back after they started to recreate there personalization’s. does anyone have any ideas on how to turn it off currently as a workaround?
Try the following code to disable them…
under initializecode
EpiUltraGrid yourGrid = (EpiUltraGrid) csm.GetNativeControlReference(“Guid”);
yourGrid.DisplayLayout.Override.AllowRowFiltering = DefaultableBoolean.False;
Pierre
Ran into this myself today testing on 10.2.500.6, and just looked up the ticket details in EpicCare.
TLDR; Definitely a bug, but you should be able to hack the customization xml to fix it if you really want to. Here’s what they put in the ticket:
PROBLEM:
Issue with layout XML created after changing a grid (e.g. column order), 13000 lines of unwanted xml is created when a grid is saved
ANALYSIS:
Initial issue was thought to be just the problem where Saving Layouts after changing a grid, the grid will default to using Grid Filters and this would always default to on. The issue was is linked to: PRB0218737/ERPS-130619
However, I am raising this new Problem with a higher priority as the above is just logged as a Cosmetic issue and this problem has a much higher impact for the customer.
Testing from within CSG suggests this issue appeared in 10.2.500 and was not present in 10.2.400. The customer has also done additional analysis of the issue and there is a much bigger problem here for the customer:
There is a method in Ice.Lib.Framework.EpiUltraGrid (in Ice.Lib.EpiClientLib.dll) called LayoutSaveAsXML
It has a line of code which does this:
this.AddGridPropertyRow(this.dsLayout, PropertyCategories.ColumnFilters);
This code doesn’t check if any filters are in place, just whacks an enormous chunk of XML into the DisplayLayout for the grid in the customisation as a “ColumnFilters” property.
This piece of code doesn’t exist in the same method at 10.0.700.4.
Looking at the surrounding code, I think the intention of this code is probably just to record a true / false value to maintain the state of the column filter visibility in the customisation. But as it stands its not doing that.
If you were to hack the ColumnFilters property out of exported XML for the filters are no longer showing for the previously affected grid.
There doesn’t appear to be any configurable way around this issue – it would need to be fixed in EpiClientLib.
Let me add a bit more detail. The code that has been introduced in 10.2.500 creates 13000 lines of unwanted xml when a grid is saved.
This is handicapping our update progress as we can’t sign off any grids. Even if you just change the frame size and save it creates grid filters and you can’t get rid of them. We really need to know that this can be fixed urgently. We could not contemplate going live with this solution.
Has this bug been fixed? I am encountering this exact same issue. I am on 10.2.500.12 and after I hid some of the columns, the grid filters start to show up.
What is the best way to rearrange columns for users??
No we are on 600.3 and it does the same thing. As soon as you touch a grid the filters kick on.
Just to add a note: This problem was fixed in ERPS-120619 in what will the the fall release 10.2.700. We also patched it back to 10.2.600.5 and 10.2.500.19
Assuming you are referring to the original issue reported in that problem then updating should resolve it for you.
