YaqoobAlam commented on issue #20604:
URL: https://github.com/apache/superset/issues/20604#issuecomment-3077847111

   We have deployed latest Superset version 4.1.2 and we are facing this same 
issue. Only the creator of the saved queries can see when a user click on a 
saved query link from another person they will see a new SQL lab editor and an 
error "The query couldn't be loaded".  When we looked into the Superset DB we 
can see all the queries have the owners. Till the resolution of this is there a 
way we can add multiple users so that they can see the same query and nothing 
breaks. Below are our saved_query table for now.
   
    id |                                      label                             
         | created_by_fk | user_id 
   
----+---------------------------------------------------------------------------------+---------------+---------
     1 | Stage Incidents V2                                                     
         |             5 |       5
     2 | Activity_incidents                                                     
         |             5 |       5
     7 | SFA_Revenue Detail Weekly                                              
         |             7 |       7
     9 | SFA_Revenue Detail Monthly (MRR)                                       
         |             7 |       7
    21 | Motaz Task II                                                          
         |            16 |      16
    10 | SFA_Operations Detail Weekly                                           
         |             7 |       7
    11 | finding_which_classroom_attended_session                               
         |             8 |       8
    13 | Calls RD                                                               
         |            16 |      16
    14 | Telesales Leads N2                                                     
         |            16 |      16
    15 | Calls Dashboard                                                        
         |            16 |      16
    16 | Potential Students                                                     
         |            16 |      16
    18 | N2 Transactions RD                                                     
         |            16 |      16
    20 | RFM RD                                                                 
         |            16 |      16
    23 | Counting # Sessions by time buckets                                    
         |            19 |      19
    25 | Blocked and reported students query                                    
         |            19 |      19
    26 | App Sessions with B2B attendees                                        
         |            19 |      19
    28 | CALLED                                                                 
         |            13 |      13
    31 | new_practise_aggregate                                                 
         |            13 |      13
    29 | Transaction                                                            
         |            13 |      13
    27 | LEADS                                                                  
         |            13 |      13
    30 | test                                                                   
         |            14 |      14
    32 | new_raw_practice_data                                                  
         |            13 |      13
    33 | 2025-07-15 - activity incidents (removed survey temps)                 
         |             5 |       5
    34 | Yaqoob-test-query                                                      
         |             3 |       3


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to