Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

how to rebind the updated data to the angular tree grid. #33

Open
medojusrinivas opened this issue Mar 27, 2020 · 5 comments
Open

how to rebind the updated data to the angular tree grid. #33

medojusrinivas opened this issue Mar 27, 2020 · 5 comments

Comments

@medojusrinivas
Copy link

I am updating the data in some other component and trying to reload the same in angular tree grid.

If I rebuild whole grid array and bind it to the angular tree grid then it is losing the collapse and expand feature. So, if I just update the element and expecting the change in the value then it is not showing in the table. I mean the updated data is not getting updated in the table.

Is there any way where if I can rebind the data again to the angular tree grid

@Dobermaxx99
Copy link

you could try to manually implement local change detection

ex
this.changeDetectorRef.detectChanges();

@medojusrinivas
Copy link
Author

can you give some example. As it is not working for me.

@medojusrinivas
Copy link
Author

Implemented the local change detection in the module but it still did not reflecting in the UI. Actually the objects in the array will be have the updated attribute and that should get reflected in the UI. I tried almost all the ways possible but nothing is reflecting it in the UI. In the console the object in array is updating the attribute value. I got struck on this from so long. If I cannot resolve I think I have look out for the new one.
please do the needful...

@cascesme
Copy link

@medojusrinivas hello did you find a solution to your problem? If not which other library are you using ? Thank you very much.

@medojusrinivas
Copy link
Author

I just kept the same old code but did some tweeks accordingly. But I suggest you look into different one as it is having lot more issues then expected. For now it is working as required but if I get new requirements I don't know what more tweeks I shud make.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants