murattkoc opened a new issue, #41454:
URL: https://github.com/apache/superset/issues/41454

   ### Bug description
   
   ### Bug Description
   
   When attempting to view or edit a role in Apache Superset v6, the 
permissions list fails to load properly. Instead of displaying the 
human-readable permission names, it only displays internal database IDs (e.g., 
`7`, `15`, `30`). 
   
   The UI throws an error: **"There was an error loading permissions"**. 
   
   Looking at the browser developer tools (Network tab), the backend API 
returns a `400 Bad Request` with the following error payload:
   ```json
   {"message": "Filter column: id not allowed to filter"}
   
   ### Screenshots/recordings
   
   ### Bug Description
   
   <img width="1744" height="761" alt="Image" 
src="https://github.com/user-attachments/assets/755b48c8-ef13-4e8e-ac65-83d7cd08ef59";
 />
   
   <img width="1744" height="761" alt="Image" 
src="https://github.com/user-attachments/assets/d527f944-687a-4815-811d-774658c1ba0b";
 />
   
   When attempting to view or edit a role in Apache Superset v6, the 
permissions list fails to load properly. Instead of displaying the 
human-readable permission names inside the select dropdown, it only displays 
raw internal database IDs side by side (e.g., `7`, `15`, `30`, `31`) without 
any accompanying descriptive text.
   
   The UI throws a toast error: **"There was an error loading permissions"**. 
   
   Furthermore, when inspecting the browser (Developer Tools / Console & 
Network tabs), there are multiple distinct errors visible:
   1. The backend API returns a `400 Bad Request` with the following error 
payload:
      ```json
      {"message": "Filter column: id not allowed to filter"}
   
   ### Superset version
   
   6.1.0
   
   ### Python version
   
   3.9
   
   ### Node version
   
   16
   
   ### Browser
   
   Firefox
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [ ] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [ ] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [ ] I have checked Superset's logs for errors and if I found a relevant 
Python stacktrace, I included it here as text in the "additional context" 
section.


-- 
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