[GitHub] [superset] nogreintel opened a new issue #17952: Feature Request

[GitBox <gi...@apache.org>]

nogreintel opened a new issue #17952:
URL: https://github.com/apache/superset/issues/17952


   **Is your feature request related to a problem? Please describe.**
   When using the superset api to create dashboards, the current api only accepts the following inputs:
   `{
     "css": "string",
     "dashboard_title": "string",
     "json_metadata": "string",
     "owners": [
       0
     ],
     "position_json": "string",
     "published": true,
     "roles": [
       0
     ],
     "slug": "string"
   }`
   If one wants to create a dashboard entirely defined in this single api call for a post to /dashboards/, even when defining the relevant charts in position_json, those charts are not recognized, and show up as non existent in superset, because the api doesn't accept the necessary data for slices and datasources.
   
   **Describe the solution you'd like**
   It would be ideal if the superset api for post to /dashboards/ would accept the following parameters:
   `{
     "css": "string",
     "dashboard_title": "string",
     "json_metadata": "string",
     "owners": [
       0
     ],
     "position_json": "string",
     "published": true,
     "roles": [
       0
     ],
     "slug": "string",
     "slices": []
     "datasources": []
   }`
   
   **Describe alternatives you've considered**
   The current workaround is to define a superset dashboard in a json template and then use the /dashboard/import api. 
   
   **Additional context**
   Add any other context or screenshots about the feature request here.
   


-- 
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-unsubscribe@superset.apache.org

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



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

[GitHub] [superset] geido commented on issue #17952: Feature Request for added dashboard api creation functionality

[GitBox <gi...@apache.org>]

geido commented on issue #17952:
URL: https://github.com/apache/superset/issues/17952#issuecomment-1009107114


   Hello @nogreintel thanks for the suggestion!
   
   I see the point that you are making and I understand it. However, I believe the endpoint is fine as it is to avoid the risk of polluting the endpoint with a lot of data. I am curious to learn what some other people think. @villebro what's your take?


-- 
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-unsubscribe@superset.apache.org

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



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