Upload a configuration into Lifecycle Services for electronic reporting (ER)

Note

We will not be accepting edits to this topic, because it is generated from a business process in Lifecycle Services.

The following steps explain how a user in the System Administrator or Electronic Reporting Developer role can create a new Electronic reporting (ER) configuration and upload it into Microsoft Lifecycle Services (LCS).

In this example, you will create a configuration and upload it to LCS for sample company, Litware, Inc. These steps can be performed in any company as ER configurations are shared among companies. To complete these steps, you must first complete the steps in the “Create a configuration provider and mark it as active” procedure. Access to LCS is also required for completion of these steps.

  1. Go to Organization administration > Workspaces > Electronic reporting.
  2. Select ‘Litware, Inc.’ and set it as active.
  3. Click Configurations.

Create a new data model configuration

  1. Click Create configuration to open the drop dialog.
    • You will create a configuration that contains a sample data model for electronic documents. This data model configuration will be uploaded into LCS later.
  2. In the Name field, type 'Sample model configuration'.
    • Sample model configuration
  3. In the Description field, type 'Sample model configuration'.
    • Sample model configuration
  4. Click Create configuration.
  5. Click Model designer.
  6. Click New.
  7. In the Name field, type 'Entry point'.
    • Entry point
  8. Click Add.
  9. Click Save.
  10. Close the page.
  11. Click Change status.
  12. Click Complete.
  13. Click OK.

Register a new repository

  1. Close the page.
  2. Click Repositories.
    • This enables you to open the list of repositories for the Litware, Inc. configuration provider.
  3. Click Add to open the drop dialog.
    • This allows you to add a new repository.
  4. In the Configuration repository type field, select LCS.
  5. Click Create repository.
  6. In the Project field, enter or select a value.
    • Select the desired LCS project. You must have access to the project.
  7. Click OK.
    • Complete a new repository entry.
  8. In the list, mark the selected row.
    • Select the LCS repository record.
    • Note that a registered repository is marked by the current provider meaning that the only configurations owned by that provider can be placed to this repository and, consequently, uploaded into the selected LCS project.
  9. Click Open.
    • Open the repository to view the list of ER configurations. It will be empty if this project has not yet been used for ER configurations sharing.
  10. Close the page.
  11. Close the page.

Upload configuration into LCS

  1. Click Configurations.
  2. In the tree, select 'Sample model configuration'.
    • Select a created configuration that has been already completed.
  3. In the list, find and select the desired record.
    • Select the version of the selected configuration with the status of ‘Completed’.
  4. Click Change status.
  5. Click Share.
    • The configuration status will change from ‘Completed’ to ‘Shared’ when it is published in LCS.
  6. Click OK.
  7. In the list, find and select the desired record.
    • Select the configuration version with the status of 'Shared'.
    • Note that the status of the selected version has changed from ‘Completed’ to ‘Shared’.
  8. Close the page.
  9. Click Repositories.
    • This enables you to open the list of repositories for the Litware, Inc. configuration provider.
  10. Click Open.
    • Select the LCS repository and open it.
    • Note that the selected configuration is shown as an asset of the selected LCS project.
    • Open LCS using https://lcs.dynamics.com. Open a project that was used earlier for repository registration, open the ‘Asset library’ of this project, and expand the content of the ‘GER configuration’ asset type – the uploaded ER configuration will be available. Note that the uploaded LCS configuration can be imported to another Microsoft Dynamics 365 for Finance and Operations, Enterprise edition instance if providers have access to this LCS project.