Generally, while you export the elements metadata with the dependencies and create a revision with that VQL, the dependencies will be imported by default during the deployment process. The export of server/database/element metadata can be done either by [**GUI way**](https://community.denodo.com/docs/html/browse/latest/en/vdp/administration/exporting_and_importing_the_server_metadata/exporting_the_server_metadata/exporting_the_server_metadata#exporting-the-server-metadata) from the Virtual DataPort Administration Tool or by using the [**export scripts**](https://community.denodo.com/docs/html/browse/8.0/en/vdp/administration/cluster_architectures_server_backup/using_the_import_export_scripts_for_backup_and_or_replication/export_script#export-script).
For instance, if I have to export the view created over two base views of the same data source, then I would export by right-clicking on the view and click on the Export option and also check the box **Export dependencies** to include the dependencies (along with the **Export environment specific properties** separately option) of the view from the Virtual DataPort Administration tool.
After exporting the view with dependencies, when I tried to create the revision from a VQL file and deploy the revision created using the appropriate REST APIs, the **dependencies were deployed** as per the expectations.
For more information, refer to [**Create a Revision from a VQL File**](https://community.denodo.com/docs/html/browse/8.0/en/solution_manager/administration/appendix/rest_api/rest_api#create-a-revision-from-a-vql-file) and [**Start a New Deployment from a List of Revisions**](https://community.denodo.com/docs/html/browse/8.0/en/solution_manager/administration/appendix/rest_api/rest_api#start-a-new-deployment-from-a-list-of-revisions) section of the Solution Manager Administration Guide.
Hope this helps!