github-actions[bot] commented on issue #13904:
URL: 
https://github.com/apache/dolphinscheduler/issues/13904#issuecomment-1502618215

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   Exported a workflow in one project and encountered an error while importing 
another project.
   A workflow was exported from one project, but an error was reported when it 
was imported into another project.
   
![9d66438f8dc1a0c40c2ae460361c886](https://user-images.githubusercontent.com/44601037/231042003-3d556ce9-e81f-4793-af8a-ca0f323ece98.png)
   
   
   ### What you expected to happen
   
   Ability to import workflows correctly.
   Workflows can be imported correctly.
   
   ### How to reproduce
   
   Export a workflow in one project, and then import the JSON file from the 
previously exported workflow in another project.
   Export a workflow in one project, and then import the json file of the 
previously exported workflow in another project.
   
   ### Anything else
   
   The workflow exported in the same project can be successfully imported. Is 
it because there is a projectCode in the JSON file of the exported workflow 
that it cannot be imported into another project?
   Workflows exported in the same project can be imported successfully. Is it 
because there is projectCode in the json file of the exported workflow, so it 
cannot be imported into another project?
   
   ### Version
   
   3.1.x
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)


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

Reply via email to