Insira sua conta corporativa ou de estudante para começar.
If you've created multiple environments to support the development of your database and apps, you must move changes from one environment to another environment. You can use Export resources and Import resources to move resources between environments.
Each environment contains resources, such as entities, flows, and apps, that you create or modify during the development process.
Typically, development is done in the same environment that is used by the organization's end users. This environment is known as the default environment. It's relatively easy to manage resource changes in the same environment. You validate the changes to make sure that all critical business processes and applications are functional, and then you release the app.
Sometimes, development and testing are done in separate environments, and changes are moved to the default environment when they are ready to be used by end users. There are several reasons why you might use separate environments. For example, you might have used a separate environment when you initially evaluated the system. Alternatively, you might want to minimize the risk that is involved when changes are made to the default environment. Separate environments provide isolation, because you make your changes in an environment that isn't the default environment. Depending on the extent of the risks, you might create an additional staging environment. In this case, you have a development environment, a staging environment, and a default environment.
You move resources through separate export and import processes, by using a package (.pkg) file. The package file is exported, saved to local storage, sent to the administrator of the target environment, and then imported into the target environment. The import process is often followed by validation testing to help guarantee that no critical business processes have been adversely affected.
The functionality for both resource import and resource export is available in the Environments section of the admin center. Both export and import occur in the context of a selected environment.
The export package will contain all changes to entities, picklists, permission sets, and roles. We are working to enable the export of more resource types such as apps, flows, connectors and others. This option lets you move contents of one environment to another environment.
The first step is to select a package file that was exported from the source environment. The import process validates, analyzes, and tries to import the package.
If the package is only partially applied, you receive an error message that describes what was imported and what wasn't imported.
The development process can involve changes to many types of resources. For example, if you update an app, you might add, remove, or update several entities or connections. Changes to some, and not all, resource types can be moved across environments. The following sections describe the types of resources that you can move.
You can export and import entities, picklists, and translation sets as follows:
Permission sets and roles are security resources that help control access to the database. Both can be moved across environments. After you move permission sets and roles, you should make sure that the permission sets are referenced by the appropriate roles, and that the appropriate users are assigned to any new roles. For more information, see Configure database security.
You can't move database data as part of the export and import of resources. To move data, you can use Microsoft Excel. For more information, see Import or export data.