You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After rebinding the datasource, table in UI shows no data found.
Can you handle that on the application side
No
Which versions of Angular and Fundamental Library for Angular are affected? Please, specify the exact version. (If this is a feature request, use current version.)
Fundamental Library - v0.43.18
Angular - v15
If this is a bug, please provide steps for reproducing it; the exact components you are using;
Hi team , we have many such issues where we need to refresh the datatable source and all these tables are already moved to platform tables several months ago are not working now (no code changes done) , for example after adding a new row in a table that is depending on an API call , getting input from parent component and feeding to child component that has table and so on..
hence this is a big regression for sourcing tables. pls help.
Also replicable on 0.43.19
Thanks much
Is this a bug, enhancement, or feature request?
Bug - Regression
Describe your proposal.
After rebinding the datasource, table in UI shows no data found.
Can you handle that on the application side
No
Which versions of Angular and Fundamental Library for Angular are affected? Please, specify the exact version. (If this is a feature request, use current version.)
Fundamental Library - v0.43.18
Angular - v15
If this is a bug, please provide steps for reproducing it; the exact components you are using;
Screen.Recording.2023-12-07.at.2.23.08.PM.mov
Please provide relevant source code (if applicable).
Refer above stackblitz link.
Please provide stackblitz example(s).
In case this is Accessibility related topic, did you consult with an accessibility expert? If not, please do so and share their recommendations.
Did you check the documentation and the API?
Did you search for similar issues?
Is there anything else we should know?
May be the fix for this issue #11002 is causing this regression.
The text was updated successfully, but these errors were encountered: