- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2026 04:25 AM
Thanks Vishal, but I don't think I have access to props/event objects with a Client Script? I'm using onClick() currently (like in a UI action).
I'm also not requiring records to be selected. I'm exporting all records currently in the list, filtered or not. That's the goal at least.
And I know I could look into uxf actions...and I'm afraid I might have to (they couldn't have made all of this more convoluted if they tried). I know there are "definitive guides" and lots of videos, it's still a mess of tables and mappings and do I have to go into UI Builder? It's all quite annoying.
But for now, I'm really just trying to understand if g_list is supposed to work on not here in a DA Client. All of the docs make it sound like it should, but we all know how terrible the docs are too.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2026 05:02 AM
Ok, this is not happening in our dev environment. So maybe this is just an issue with my PDI. They're both on Zurich, but guessing my PDI was zbooted to Zurich, but we upgraded to it. Maybe different patch levels too.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2026 10:20 AM
Hello @maciep
You can try to release PDI instance and then request for new PDI and try again.
Hope that helps!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2026 11:41 AM
Yeah, I might do that. And if it persists, maybe I'll try to file a bug.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2026 11:48 AM
It turns out the g_list does work, so that's good. The condition is an empty string when there is none. The userID is being returned as expected as well.
The list/view look don't really work...at least not like in the classic list. But I'm guessing that's more because lists are just different in workspaces? The main need for that info is to get the columns/fields that should be exported.
So instead, I'm getting the url with top.location.href and parsing the list-id out of it. And that is the sys_id of the record in sys_ux_list. Those records contain the associated columns.
And if it's a personallized list, there will be a record in the sys_user_preference table with the name="
