[GitHub] [superset] durchgedreht opened a new issue #13398: ID / Name label option for Filterbox

[GitBox]

durchgedreht opened a new issue #13398:
URL: https://github.com/apache/superset/issues/13398


   **Is your feature request related to a problem? Please describe.**
   In many DBs there's an ID / Name pattern. So the *id* is integer and *name* 
is String for human readable representation.
   When using Filterbox you have to decide to use id field or String field, but 
ideally you'd like to use the id field for the technical filter and use the 
name for labelling only.
   
   example table:
   <table>
   <tr>
   <th>id</th>
   <th>name</th>
   <th>revenue</th>
   </tr>
   <tr>
   <td>1</td>
   <td>sports</td>
   <td>1000</td>
   </tr>
   <tr>
   <td>2</td>
   <td>cars</td>
   <td>3000</td>
   </tr>
   <tr>
   <td>3</td>
   <td>entertainment</td>
   <td>20000</td>
   </tr>
   <table>
   
   
   Benefits would be:
   
   - User still sees a list of Strings to include (as if he selected *name*)
   - *preselecxt_fiter* option could inject INTEGER values from the outside. 
This is especially useful from an integration perspective as normally APIs and 
applications that link directly into superset and want to preselect a filter 
will work on the ID rather than on the name 
   - imagine the name is changed -this would break the 'contract' between the 
url parameters and the DB values. The argument, it's based on the data is very 
weak as names are considered dimension data and thus any data tool should rely 
on the ID field.  
   
   **Describe the solution you'd like**
   It would be great to have an option 'verbose column' (or similar) in the 
filterbox's parameters. That column selection is optional, but would take care 
about the  ID -> string mapping.  
   
   <img width="390" alt="Screenshot 2021-03-01 at 23 51 10" 
src="https://user-images.githubusercontent.com/4490840/109569700-1ef0d380-7ae9-11eb-9d3c-8f5135225a87.png";>
   
   In the UI filter box a user would just see values like 'sports', 'cars', 
'entertainment', but it could be controlled by preselect_filter using IDs 1, 2, 
3.
   <img width="326" alt="Screenshot 2021-03-02 at 00 02 26" 
src="https://user-images.githubusercontent.com/4490840/109570645-a9860280-7aea-11eb-82ae-d0111c117858.png";>
   
   
   **Describe alternatives you've considered**
   If the 'verbose' field could be entered using a dedicated SQL expression 
potentially controlled/secured by some JINJA templating, that would maby more 
technical, but also more flexible.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org