Design Pattern for Drilldown / Filtered Search

Asked
Active3 hr before
Viewed126 times

4 Answers

patterndesign
90%

The tables above constitute the bulk of the data, and it is complemented by tables storing the [logical] schema of the catalog, also known as the "metadata". These tables include:,Storing the data "vertically", i.e. in an Entity-Attribute-Value (EAV) format, along with the [meta]data-driven schema management implicit to EAV, provide a framework where each product's attributes are "independent" from one another. This, in turn, facilitates the implementation of drill-down (i.e. guided refinement of the query, where at each step the end-user is supplied with the list of possible attributes still applicable, for each such attribute the list of possible values).,Entity (aka a product, or an item) = a "record" in the traditional relational lingo,Asking for help, clarification, or responding to other answers.

With EAV, the bulk of the information is stored in two tables called say the Product table, and the ProductAttributes table:

Product table
   "ProductID"(primary key, the "EntityId")
"TypeId"
optionally, some common attributes found in all / most other Products, say...
   price
ManufacturerId
Photo

ProductAttributes table
   "ProductID"(Foreign Key to Product table)
"AttributeID"(FK to Attribute table)
"Value"(actual value; note: sometimes we can have several SQL fields
   for this say IntValue, StringValue, DateValue, allowing to store values in their natural format)
load more v
88%

The drilldown report pattern consists of a bar chart and column chart, which each drill down into a grid. This page explains how you can use this pattern in your interface, and walks through the design structure in detail.,This pattern introduces a 408-line expression to the interface.,You can click on these graphs to drill down to detailed information about your data. This is a variation of the grid with detail pattern Use this pattern if you want to drill into a set of data that is displayed in a grid., Interface patterns give you an opportunity to explore different interface designs. Be sure to check out How to Adapt a Pattern for Your Application.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
load more v
72%

Open the [Logs] Web Traffic dashboard, then set a search and filter., Open the [Logs] Web Traffic dashboard. , Open the [Logs] Web Traffic dashboard, then set a search and filter. Search: extension.keyword: ("gz" or "css" or "deb") Filter: geo.src: CN ,Use the Sample web logs data to create a dashboard and add panels, then set a search and filter on the [Logs] Web Traffic dashboard.

https: //github.com/elastic/kibana/issues?q=is:issue+is:open+{{event.value}}
65%

One of the important considerations for the details page is the name of this page. This name is what you will see in the drill through option from the master page. It should be something that gives the user the understanding that this is a details page.,Now let’s see how this drill-through functionality works. Go to the master page, and right-click on a column in the column chart that has education as part of its axis, then you will see a Drillthrough option that will lead you to the details page.,The challenge that you may face now is what if in the master page, someone uses the Drillthrough option, on a chart that doesn’t have Gender on it?,“Keep all filters” option means it will pass any filter from the master page to the details page, even if you have not added that field in the Drillthrough section of the details page. If you turn this feature off, then Drillthrough only works for pre-defined fields.

Or another approach is to get help from DAX. You can write a simple DAX expression to find out what are the selected values. You can create a measure with expression below:

Selected Gender = SELECTEDVALUE(DimCustomer[Gender], "All")