Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
hi All,
I'm throwing this one out there for discussion. I have a feeling that I've seen it discussed before, but can't find the thread!
Regularly I will have a large table that I will then need to retrieve distinct values of dimensional fields from in order to display in selection boxes etc. This obviously impacts the load significantly as it has to load the full table each time.
Any ideas on ways to improve this process? (Flags, group by's etc.)
Thanks!
ps. As pointed out below - the reason for doing this is that I need a separate table that is not linked to the main table
The list box actually displays distinct values of any column, so why do you have to load distinct values ?
A List Box shows the values distinct by default.
Since you probably already knew that, my guess is your actual problem is a bit different. Please explain your actual problem / challenge.
I need it to be an independent dataset (ie. not linked to the 'main' table)
How about this:
SomeIndependentTable:
LOAD DISTINCT
SomeFieldName
RESIDENT OriginalTable;
Thanks OvK, that's the technique that I've been using but was hoping for any better performing alternatives...
Hi Julian
Its an interesting topic, and I have a similar issue. It does seem strange that a load from a large table is slow even when the resulting data is minimal. I hope there will be some further comments.
regards
then use alternate states if you want to have "in a different dataset"
Not that straightforward I'm afraid... I need to, for example, have date selections to apply to the start of a waterfall chart and the end of the same waterfall chart.
then use Claendar control and link them to 2 variables then you expression will have in the where condition somthing like this:
sum({<Date={">=$(fromDate) <=$(ToDate)"}>} Metric)