Export setup

Highly-detailed extrusion profiles are also affected for these items. Extra Low Low Medium High. Selects the phase of the document to export, defaulting to the last phase of the document. If "Export only elements visible in view" is selected on the Additional Content tab, the phase of the view is used and this option is disabled.

Split Walls, Columns, Ducts by Level. Allows you to divide multi-level walls, columns, and ducts by level. When you use this option, Revit cuts the walls, columns, and ducts by each level that is defined as a building story see Level Instance Properties.

Opens the File Header dialog, which allows you to enter author and organization information. Opens the Project Address dialog, which allows you to provide information about the project purpose and location. Select the "Update project information" option to save the information to the project.

Select this option to include 2D elements supported by IFC export notes and filled regions. Clear the option to exclude these elements. Select this option to export Revit links in the model as separate IFCs. Clear this option to exclude Revit links. Each linked instance in the file is exported as a separate IFC file with the correct positioning relative to the host file.

Multiple instances of the same linked document are exported as separate files, identical except for their position and orientation. If the "Export only elements visible in view" option is selected, selecting this option exports all rooms contained inside the section box of the selected 3D view.

In the Setup and Maintenance work area, select the offering you want to export from the Offering menu. For an entire offering, select and open the Actions menu in the page header, and then select Export. For a specific functional area, select and open the Actions menu corresponding to the functional area, and then select Export. Optionally, specify appropriate scope values to filter exported setup data. By default, all existing setup data is exported for each business object processed during export.

However, if scope is supported by any of those business objects, you can select scope values to filter the exported setup data. To specify scope values for one or more of the business objects:.

Select the applicable business object from the Business Objects table and then click Add. If no related business object supports scope, then the table remains empty.

Search and select the value you want to use as scope for the business object and click Apply. Repeat the previous step to add more scope values if needed.

Click Done when finished. Monitor the status of the export process until it completes by selecting Export from the Actions menu.

Up to three most recent processes are listed, and are ordered from newest to oldest. Each process indicates its status at the time, and if it was completed already, then the time stamp when it was processed. While the process is still in progress, you may select the status to view how much progress the process has made at the time.

A message shows you how many business objects were already processed out of the total number of objects to be processed. Click View Progress to review the details on the business objects that were already processed. Click the Refresh button to get the most recent information. Refer to the topic Review of Export and Import Process Results for detailed description of the process results. When the export process completes, select the status link to go to the Export Offering Data Results page.

If the process completes successfully, the status is set to Ready to download. Click Download File to download the configuration package. Use this file to import setup data in the target environment. In addition, review the list of post export tasks. If any tasks are listed, then those tasks aren't migrated by export and import process. You must migrate that data manually in the target environment.

On the other hand, if the process completes with errors, the status displays Ready for error review. The Business Objects table shows all business objects that had errors during processing. Click Download Log File from the page header, which includes the error log of all business objects that experienced error. After correcting the cause of the errors, create a new export process. If there were any changes to the setup data since the previous export, you don't have to export the entire setup data all over again for an offering or a functional area.

Instead, you can select and export only the specific setup data that changed. However, make sure that the prerequisite data was already migrated to prevent any errors during import.

This procedure shows you how to export a subset of setup data using an offering or a functional area. To export a subset of setup data using an offering or a functional area, follow these steps. In the Export column, deselect the check boxes of business objects that you want to exclude from the export.

Business objects with a check mark remain selected for export. If the setup data in any of the excluded business objects is a prerequisite for the imported setup data in the target environment, then the import might fail. Therefore, exclude or include business objects after assessing the dependencies, if any. If the export service used by the selected business objects is also associated with any business object that you excluded, you're prompted to either export all related business objects or none of them.

By default, all existing setup data is exported for each selected business object processed during export. For instance, the excluded business objects are listed in the Manual Tasks section. You can download the Manual Tasks Report from the Actions menu. This procedure explains how to import setup data for an offering or functional area.

You also need access to additional roles if you're importing certain business objects. For more information about additional roles to import these business objects, refer to the topic Additional Access Required for Exporting and Importing Setup Data. To import setup data for an offering or functional area, follow these steps.

In the Setup and Maintenance work area, select the offering you want to import from the Offering menu. If the configuration package you want to import was created by exporting:. An offering, select Import from the Actions menu in the page header. A functional area, select Import from the Actions menu corresponding to that functional area. Browse and select the configuration package file that contains the setup data you want to import.

View the Configuration Package Details to verify that you selected the correct file. If the offering or functional area selected during export doesn't match the offering or functional area you chose for the import process, an error message appears. Click the Update button to browse and select the correct file.

Best practice is to select the Compare setup data prior to import option. If you select this option, the import process automatically runs a comparison of the setup data in the configuration package file with that in the target environment before importing the setup data. Optionally, select the Import feature selection option to import the opt-in configuration of the offering or functional area you're importing.

This imports the enabled dependent functional areas and features of the offering or functional area. The Pause process each time an error occurs option is selected by default. If an error occurs, the import process pauses so that you can take corrective action and resume the import. If you don't want the import process to be interrupted even if there are errors, deselect the option.

However, note that if any prerequisite data fails, additional dependent data might not be imported correctly. The Pause process each time manual import setup data is required option is selected by default. The import process pauses each time there's some data that you must manually import.

You can deselect this option if the data to be imported manually already exists in your target environment. If any setup data requires manual entry before the import can start, a warning message appears.

This message shows you the tasks you must perform before submitting the process. If you verified that the setup data for those tasks are already entered in the target environment, click Submit. Otherwise, click Cancel.

Create a new import process after you ensure that the setup data is entered in the target environment. Up to three most recent processes are listed and ordered from newest to oldest. Each process indicates its status at the time and, if the process is completed, the time stamp when it was processed. While the process is in progress, you can select the status to view how much progress the process made at the time.

A message shows you how many business objects were already processed out of the total number of the objects to be processed. Click View Progress to review the details of the business objects that finished processing. Click the Refresh button to view the most recent information. Refer to the topic Review of Export and Import Process Results for detailed information about the process results.

If you selected the Compare setup data prior to import option, once the comparison completes, the status reads Waiting for comparison review. Select the status to go to the Import Offering Data Results page to review the comparison results. Click Continue to Import from the Import Offering Data Results page to start the import process if you're satisfied with the comparison results. Alternatively, if you didn't select the Compare setup data prior to import option, the import process starts automatically.

If any setup data requires manual data entry during import, the process pauses, and the status reads Waiting for manual import. Select the status to go to the Import Offering Data Results page and review the details. A list displays the business objects that require manual data entry before import. For each of the listed business objects, click Go to task. This displays a list of related tasks. Select each task to enter the required data.

After you enter the setup data for all the listed business objects, click Resume from the Import Offering Data Results page to restart the import process. Click Confirm in the confirmation message that appears to resume the import process.

If any post import tasks are listed, ensure that their setup data is entered. Otherwise, the setup data remains incomplete, and you experience errors when processing transactions. The Business Objects table displays all business objects which encountered errors while processing. Refer to the topic Review of Export and Import Process Results for a detailed description of the process results. Click the Download Log File from the page header level. This includes the error log of all business objects that encountered errors.

This procedure explains how to compare setup data for an offering or functional area during the import process. To compare setup data for an offering or functional area during an import process, follow these steps. Best Practice is to select the Compare setup data prior to import option. This topic explains how to compare setup data outside of the import process. You also need access to additional roles to compare certain business objects. For more information about access to additional roles, refer to the topic Additional Access Required for Exporting and Importing Setup Data.

You can compare setup data using offering or functional area, in either of these ways:. Compare setup data in one configuration package with another configuration package. Compare setup data in one configuration package with the setup data in the environment. In the Setup and Maintenance work area, select the offering whose setup data you want to compare. If the configuration package you intend to compare was created by exporting:.

For Configuration 1, upload the base configuration package file whose data you want to compare with that in the environment or with another configuration file.

To upload the configuration package file, follow these steps. Click the Configuration Package list and select Upload new. Browse to find the configuration package file, select it and click Open. Optionally, open Configuration Package Details to verify that you have selected the correct file. If it's not the correct file, then click Update to browse and select the correct file. For Configuration 2, the option Data in this environment is selected by default to compare with the existing data in the environment.

But if you want to compare with another configuration package, click Source and upload another configuration package file. Once the sources are ready, the process for setup data comparison is ready to be submitted.

Optionally, you can change the default process name that's automatically assigned. Up to three most recent processes are listed and are ordered from the newest to oldest. Each process indicates its status at the time and, if the process has completed, then the time stamp when it was processed. When the process completes, the status shows Ready for comparison review. Select the status to go to Comparison Process Results to review the details of the results.

Refer to the topic Setup Data Comparison Results for detailed descriptions of the comparison results. If you used an implementation project to enter setup data, then you can use your implementation project to export and import setup data. In this alternative method, the tasks in your implementation project and their sequence determine the list of setup business objects whose data is exported and imported, and in which order.

Select your implementation project, and create a configuration package to generate the ordered list of business objects for export and import. The implementation project you use to create a configuration package must contain only one offering. The import process fails otherwise. If you included multiple offerings in an implementation project to enter setup data, don't use it to create a configuration package for setup data export and import.

Instead, create new implementation projects with only one offering in each, and use these to create separate configuration packages. Although best practice is to select an offering and its functional areas to create an implementation project, you may have created an implementation project by selecting specific tasks and task lists instead.

Such implementation projects are often created to update and maintain a small set of setup data after the initial migration of an offering to a target environment has completed. When using such implementation projects to create configuration packages for setup data export and import, consider the following requirements carefully to ensure the success of the process:. If any setup data in the configuration package has a dependency on any other setup data, then that prerequisite data must be available in your target environment before you start the import process using the configuration package.

Otherwise, consider including the prerequisite task in the implementation project before you create the configuration package. The sequence of the task list and tasks, and therefore the business objects, in your implementation project must align with the setup data dependency requirements.

The import process may fail if you don't ensure the correct order of the task lists and tasks in the implementation project. When using an implementation project to migrate setup data, the comparison report isn't integrated with the import process. However, best practice is still to compare the setup data in the exported configuration page with the data existing in the target environment before starting the import process.

This procedure explains how to export setup data for an implementation project that you already completed setting up. For more information about access to the additional roles, refer to the topic Additional Access Required for Exporting and Importing Setup Data.

Select the implementation project you want to use for the setup data export from the Name menu. Leave the default selection for Export, Setup task list and setup data , unchanged. In Configuration Package Details, you can use the default field values for Name , Code and Description , or assign unique values. The first table displays the list of business objects whose setup data is exported.

The implementation project you selected as the source of this configuration package in the previous step determines the business object list. The Type column indicates the export and import behavior of the business object as follows:.

If export and import services are available for a business object then the type is business object service. If the type is specified as Scope , then the business object can be used to select a scope value to filter the exported data. However, the setup data of the business object itself in not exported. If the setup data of any business object must be migrated manually using alternative methods that are external to setup export and import processes, the type is Manual data loading.

All business objects whose type is Business object service have their Export column checked by default. You typically keep this selection unchanged.

When you select a business object in the first table, if it supports scope to filter exported setup data, you can select appropriate scope values in the second table. If the business object you selected has predefined scope values, then scope table lists all of them by default. You could decide to remove one or more of the listed scope values but you can't add other values.

If the business object you selected supports scope but doesn't have predefined value, then you can add one or more scope values. Search and select each of the values you want to use as scope to export data for and click Apply.

Click Submit to submit the setup data export process and confirm when the confirmation message appears. Monitor the process from Manage Configuration Package until it completes. For the two export modes, two cron definitions can be configured. If cron definition is empty, export is not executed.

The actual export then is processed via Symfony messenger queue. In the Loggers tab you can define the logging parameters. Settings like this should be enough most of the time After the configuration you can run the command manually with the Execute button, or the cronjob is executing it if you have defined it in the configuration. Any additional feedback? Note You will need Azure Active Directory global administrator rights to perform these steps.

Note When you are working in the Azure portal, you will be instructed to save several values for subsequent steps. Note Don't make any changes to the fields, Assign access to and Azure AD user, group, or service principal.

Note If you use this approach, you must select a Power Platform environment that is in the same region as your Finance and Operations environment. Submit and view feedback for This product This page. View all page feedback. In this article. The name of the storage account created earlier.

Sign in to the Azure portal and open the Azure Active Directory service. Open the Properties page and copy the value in the Directory ID field. This name should have been previously saved. Enter the DNS name of your key vault. If you used the suggested name, enter storage-account-name. If not, enter the secret name you defined.

If you used the suggested name, enter app-id. If you used the suggested name, enter app-secret. Application ID provided is incorrect or can't be found. You might have to contact the system administrator or the administrator who configured Azure resources. The application ID app-id and application secret app-secret that are provided can't be used to access the storage account.

Next, verify that the application has the required access to the storage account. StorageNameUserError : Failed to access the storage account using the storage name provided in the key vault. The storage account that is provided in the key vault can't be found, or it isn't valid. Verify that the correct storage account name is entered in the key vault by following the steps in Configure export to Azure Data Lake - Add secrets. Verify that you've provided the correct secret name for the storage account by following the steps in Configure export to Azure Data Lake Add secrets.

The service can't access the key vault or the secrets in it. Verify that your Azure subscription hasn't expired.