I've been trying to reimplement our user created list views as table filters on the Skuid pages (since there is no exact Skuid equivalent of that and filters is the closest thing). Some of the views contain grouping logic (AND/OR between conditions). It seems there is no way to specify a single table filter selection (one click) with grouping logic for its multiple conditions. All the conditions are ANDed, as far as I can see.
If someone got a better solution, I'd like to hear it, otherwise this would be a nice addition. :)
If someone got a better solution, I'd like to hear it, otherwise this would be a nice addition. :)
-
284 Points
Posted 5 years ago
Pat Vachon, Champion
-
46,404 Points
Rob Hatch, Official Rep
-
45,308 Points
-
2,468 Points
(I understand that the list views of salesforce you are mentioning are the views of the default tabs in salesforce, if don't, don't continue reading xD)
you can try to do a tab set with the tab navigation in "listview" and play with the rendering conditions of each tab (And on each tab a table associated with a model with all the and/or condition logic for that view).
you can try to do a tab set with the tab navigation in "listview" and play with the rendering conditions of each tab (And on each tab a table associated with a model with all the and/or condition logic for that view).
Rob Hatch, Official Rep
-
45,308 Points
That is good creative work! It does have a few down sides..
Unless you are willing for your users to add models, tables and tabs to your page it is not really "user configurable" (It might be arguable that the Salesforce list view definition is not super accessible to end users either, but I digress...)
In this approach you are creating separate models and tables for every view (every tab). This means increased weight on initial page loads. You could put each of these tab options in a page include which would mitigate that problem, but would introduce its own complexity.
Again - good work!
Unless you are willing for your users to add models, tables and tabs to your page it is not really "user configurable" (It might be arguable that the Salesforce list view definition is not super accessible to end users either, but I digress...)
In this approach you are creating separate models and tables for every view (every tab). This means increased weight on initial page loads. You could put each of these tab options in a page include which would mitigate that problem, but would introduce its own complexity.
Again - good work!
Shmuel Kamensky, Champion
-
4,700 Points
Shmuel Kamensky, Champion
Shmuel Kamensky, Champion
https://andyinthecloud.com/2014/09/20/super-listview-viewer-using-winter15-listview-api/
https://community.skuid.com/skuid/topics/can-we-pull-object-metadata-into-a-skuid-page
Pat Vachon, Champion
Not sure how one can override the SOQL though. Seems like a franskentien solution would be born though.
Shmuel Kamensky, Champion
skuid.model.getModel('modelId').soql = 'select id from Opportunity';Pat Vachon, Champion
Pat Vachon, Champion
Pat Vachon, Champion
Shmuel Kamensky, Champion
Going over this I think I made a mistake. I've been overriding 'orderByClause.' That currently works. But I've not been getting
skuid.model.getModel('modelId').soql = 'select id from Opportunity';to work. Skuid may have stopped supporting it. But I can't find anywhere that I used it. So more likely I made a mistake. Sorry to get your hopes up! I think you're right in that it would take some monster making to get this working from the metadata info. :(