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

   ### Bug description
   
   We are trying to implement automation of export of dashboards from one 
superset installation to another and have written code snippets in the two 
files in attached zip file:
   
   [export.zip](https://github.com/apache/superset/files/15405376/export.zip)
   
   When we try to run python export_assets.py we are getting following error:
   
   requests.exceptions.HTTPError: 422 Client Error: UNPROCESSABLE ENTITY for 
url:
   
   
   ### How to reproduce the bug
   
   activate python virtual environment for superset in a putty session after 
logging as superset installation user.
   
   copy both files in zip file to the above putty session.
   
   run python export_assets.py
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   3.1.3
   
   ### Python version
   
   3.9
   
   ### Node version
   
   16
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   Please note that following feature flags are enabled on instance where we 
are trying the above code and superset version on this instance is 3.1.1:
   
   
                    "ALERT_REPORTS": True,
                   "VERSIONED_EXPORT": True,
                   "DASHBOARD_CROSS_FILTERS": True,
                   "ENABLE_JAVASCRIPT_CONTROLS": True,
                   "DASHBOARD_RBAC": True
   
   
   ### Checklist
   
   - [X] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [X] 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