Angular UI grid column filter doesnt appear after pin / unpin column:

[JaydeepPatoliya]

down vote favorite I am using latest version of angular UI grid.

Angular UI grid filter doesn't appear after pin / unpin column:

Steps to follow:

Pin any column (Email / phone) etc. Unpin same column Now click toggle filtering button Textbox for filtering on same column doesn't appear I have created Plunker to demonstrate this:

Plunk Demo

I tried refreshing grid / notifyDataChange, but seems doesn't work. Please suggest possible solutions.

[JaydeepPatoliya]

Hi All,

Can anyone face same problem? I am stuck to find solutions. Appreciate if anyone find this solutions. Thank

[mportuga]

I am working on it

[BhagyashriJ]

I am also facing same issue. Is there any workaround to resolve this.

[JaydeepPatoliya]

@mportuga is there any update?

[mportuga]

None yet.

[feehong]

gridApi.pinning.on.columnPinned($scope, function (colDef, container) { if (isRenderingComplete && !container) { var gridCol; angular.forEach($scope.gridApi.grid.columns, function (val) { if (val.field === colDef.field) { gridCol = val; } }); if(gridCol) { uiGridGridMenuService.toggleColumnVisibility(gridCol); $timeout(function () { uiGridGridMenuService.toggleColumnVisibility(gridCol); }, 0); } } });

[ThCC]

Hi everyone So this issue still happens. I'm using the last published version, with a custom modification, and for what I gather from debbuggin is this:

When I unpin the method updateHeaderOptions runs before the event $destroy hits, wich makes the $scope.col.filterable become undefined, and the filter input vanish. When I pin the exact opposite occurs, and everything gets corrected.

Do you @mportuga have any ideas? I need to put this to work, even though it takes time to be release in the official version.

[BreTuck]

Hello Everyone,

Have there been any updates on this fix? The company that I work for is still facing this issue. I was wondering if a solution has been tested to be incorporated into a future release? If not, is there any plan for resolving this issue and what is the associated timeline?

Thank you for any information that you can provide.

[deeprajmaurya]

Hey Everyone, Any update on this issue?

[ThCC]

Hi everyone So this issue still happens. I'm using the last published version, with a custom modification, and for what I gather from debbuggin is this:

When I unpin the method updateHeaderOptions runs before the event $destroy hits, wich makes the $scope.col.filterable become undefined, and the filter input vanish. When I pin the exact opposite occurs, and everything gets corrected.

Do you @mportuga have any ideas? I need to put this to work, even though it takes time to be release in the official version.

Hey Everyone, Any update on this issue?