Feedback Edit

Microsoft Power Platform plug-in admin reference

  • Article
  • 3 minutes to read

Important

Some or all of the functionality noted in this article is available as part of a preview release. The content and the functionality are subject to change. For more information about preview releases, see Service update availability.

This article provides information about how to set up and configure the Electronic invoicing solution in Microsoft Dataverse.

Prerequisites

The following requirements must be met before you configure the Dataverse solution for Electronic invoicing:

Getting the solution

The Dataverse solution for Electronic invoicing (Microsoft Dynamics 365 Electronic Invoicing connector for Microsoft Dataverse) must be installed from AppSource. After the installation process is complete, make sure that the msdyn_MicrosoftDynamicsElectronicInvoicing solution appeared in the solutions list in Dataverse. This solution adds a list of Electronic invoicing entities that contain audit and log information for electronic invoicing submissions. The solution also adds a business logic plug-in that implements communication with the Electronic invoicing solution.

Authentication and authorization

After the solution is imported into the Dataverse environment, the finance and operations apps environment and the Dataverse environment must be set up to connect to each other. Dataverse will call finance and operations apps by using Service-to-Service (S2S) authentication, based on an Azure Active Directory (Azure AD) application. The security role for finance and operations apps must be manually added by the system administrator. Different security roles can be assigned to users in your finance and operations apps. The roles that are assigned to a user (for example, the Accounts payable clerk) depend on the functions that the user requires to perform their duties. These assigned roles must have the privileges to run the corresponding virtual entities and business events.

Follow these steps to assign security roles.

  1. In your finance and operations apps, go to System administration > Users.
  2. In the list, find and select the user that you want to assign security roles to, and then select Assign roles.
  3. Select the roles to assign.
  4. Save your changes.

Follow these steps to set up the integration between environments.

  1. In Regulatory Configuration Services (RCS), go to Globalization features > Environments > Service environments, and select the target service environment.

  2. In the Dataverse endpoint URI field, enter https://<Dataverse organization URL>/api/data/v9.1/.

  3. In your finance and operations apps, go to System Administration > Setup > Azure Active Directory applications to register Dataverse.

  4. Add a row.

  5. In the Client ID field, enter ecd93392-c922-4f48-9ddf-10741e4a9b65.

  6. In the Name field, enter Microsoft Dataverse Integration.

  7. In the User ID field, select the user that you assigned security roles to in the previous procedure.

  8. Go to Organization Administration > Setup > Electronic document parameters > Dataverse integration.

  9. Register a new app. For more information, see Register the app in the Azure portal.

  10. Set up the Azure key vault, and put the app secret there. For more information, see Set up the Azure Key Vault client.

  11. On the Dataverse integration page, on the Dataverse integration tab, enter the app ID and secret.

  12. Create an application user in Dataverse, and associate it with the app ID. For more information, see Create an application user. This user should be assigned a security role that has privileges to read and write the following Dataverse entities:

    • Electronic Invoice Submission
    • Electronic Invoice Submission Document

  13. Create another application user in Dataverse, and associate it with the app ID ecd93392-c922-4f48-9ddf-10741e4a9b65. This user should be assigned the Finance and operations Basic User security role and a role that has privileges to read and write the following Dataverse entities:

    • Electronic Invoice Action
    • Electronic Invoice Execution
    • Electronic Invoice Submission
    • Electronic Invoice Submission Document

Enabling virtual entities

The Dataverse solution for Electronic invoicing for Indonesia depends on a set of virtual entities that must be enabled before you run the Electronic invoicing scenario. Because so many entities that are enabled for Open Data Protocol (OData) are available in finance and operations apps, the entities aren't available as virtual entities in Dataverse by default.

For more general information about how to enable virtual entities in Dataverse, see Enable Microsoft Dataverse virtual entities.

For Indonesia, the following virtual entities must be enabled in Dataverse:

  • BusinessDocumentBatchSubmissionItemEntity
  • BusinessDocumentSalesInvoiceBaseEntity
  • BusinessDocumentSalesInvoiceLineItemEntity
  • BusinessDocumentProjectInvoiceBaseEntity
  • BusinessDocumentProjInvoiceCostLineEntity
  • BusinessDocumentProjInvoiceEmplLineEntity
  • BusinessDocumentProjInvoiceItemLineEntity
  • BusinessDocumentProjInvoiceOnAccLineEntity
  • BusinessDocumentProjInvoiceRevenueLineEntity
  • BusinessDocumentCustTransEntity
  • BusinessDocumentCustVendCreditInvoicingJourEntity
  • BusinessDocumentTaxGroupHeadingEntity
  • BusinessDocumentTaxTableEntity
  • BusinessDocumentTaxTransactionEntity
  • BusinessDocumentParametersEntity

Help us understand

We want to learn more about how people use Microsoft's custom Help toolkit. Take the survey (in English) and help us understand: https://forms.office.com/r/A4cUJgjkD1.