A bug occurred when the Paid Enterprise filter was searched remotely

[crazy-wang]

I used the 18.0.0 enterprise paid version
When aggridvue performs filter remote full filtering, it listens for filter change events, triggers re-call to load data setRowData, and the result filter is reset. Normally, only the row data changes, and the filter of the table header remains in the filtered state.

[AG-Zoheil]

Hi

Thank you for reporting this.

We'd be happy to look into this, but the most efficient way for us to do so would be for you to provide a live example reproducing the issue.

Please send us a live plunker sample which shows the issue. You can use one of the examples from our website as a starting point. Do let us know if you need further guidance on this.

We're looking forward to your response.

Kind regards,
Zoheil

[crazy-wang]

hi, I uploaded a demo attachment. The ag-grid-vue plug-in and the elementui plug-in need to be introduced. The usage scenario is demonstrated in the demo: The amount of data is relatively large, it will be processed by paging, the current page only shows 1000, so the filtering needs to be remote full data filtering. Initially, the header filter is obtained through the backend service, and then manually set in. Initialize the request server to render the data into the table. Listen for filter events. When the filter changed, the listening event was triggered to re-request the server data. When the data was returned and re-rendered into the table, something strange happened: the filter entry did not retain my previous filter state, but was reset. In normal cases, only table row data changes and filter is not reset。 Please replace the ajax requests in my code with your own 我爱%零零狗 ***@***.***  

…

------------------ 原始邮件 ------------------ 发件人: "ag-grid/ag-grid" ***@***.***>; 发送时间: 2024年5月17日(星期五) 晚上9:45 ***@***.***>; ***@***.******@***.***>; 主题: Re: [ag-grid/ag-grid] A bug occurred when the Paid Enterprise filter was searched remotely (Issue #7977) Hi Thank you for reporting this. We'd be happy to look into this, but the most efficient way for us to do so would be for you to provide a live example reproducing the issue. Please send us a live plunker sample which shows the issue. You can use one of the examples from our website as a starting point. Do let us know if you need further guidance on this. We're looking forward to your response. Kind regards, Zoheil — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[crazy-wang]

``

1. Using paging processing, a page display 1000; Bind the filterChanged event to the aggrid component
   

2. The filterChanged event triggers a re-request for data. This is just a setRowData. Normally, the selected filter state should be retained, but this step will report the filter state reset. 【Please change the request data api to your own for testing】
   

[AG-Zoheil]

Hi @crazy-wang,

Thanks for getting back.

I'm afraid we will not be able to use screenshots as a starting point.

We appreciate you taking the time to report any potential issues, but if you'd like us to investigate this please use one of our examples as a starting point and fork & save a plunker that you can share with us.

Please also note that v18 is now six years old. It is very likely that any issues reported for that version have already been fixed or are no longer relevant in newer versions of the grid. Therefore, please keep in mind that we would only fix issues that are present in the latest versions of the grid.

Many thanks!