CSM Dashboard gives "Method invocation failure for"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-08-2023 06:31 AM
When trying to run Dashboard reports inside CSM Workspace, I get the following error message and it will not display the report.
"Method invocation failure for: com.glide.ui.list.graphql.listLayout.ListLayout::getAllColumns"
This happens with my ID only and if I impersonate with any other user, it runs fine.
Any help is appreciated.
Regards
Kumar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2023 10:15 PM
Hi @Kumar122 ,
This error is due to batching on lists, To disable batching on lists, the new system property "glide.ui.list.batching.exclusion.list" has been created in new releases. This is a list of comma separated tables to disable batching on. Table names need to be listed according to the added options on the CSM workspace, or any other workspace encountering the same issue.
Follow the steps :
1) Create the system property "glide.ui.list.batching.exclusion.list".
2) Enter "Table_name" in the property value field, so that all seismic lists on the tables [CSM],[Incident],etc. will be unbatched.
3) Clear the cache by entering cache.do in system navigator.
4) Refresh the CSM workspace.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2023 12:31 AM
Hi @Community Alums ,
Thanks for your reply. I tried this already but still gives the same error message.
Any other ideas?
Regards
Kumar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-09-2024 09:46 AM
@Kumar122did you find a resolution to this issue? I am experiencing an issue similar and the glide.ui.list.batching.exclusion.list system property didn't resolve the issue either.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-15-2024 11:02 AM
Similarly, have tried creating this with multiple tables unbatched but still getting this error after a cache.do.
Looking for info as this is a critical issue for our team at the moment.