Enable a session time-out window of five minutes for dual-write sessions.
When dual-write is configured, only a two-minute session time-out window is available. How to obtain a five-minute session time-out window is described in this article. Versions 10.0.36.0 and later of the Dual-write core solution are compatible with this information.
The actions you need to take depend on the kind of setting you are in.
Environments for production and sandboxing
Open a support ticket with the Microsoft support team once you have configured dual-write from LCS and your power platform integrated dataverse environment is identical to the dual-write linked dataverse environment. Enable a 5-Minute Transaction Timeout for Dual Include the organisation ID or tenant ID and write DV to FinOps Transactions in the subject line. The five-minute session time-out window will be enabled for you by Microsoft.
environments hosted by customers and developers.
Finish the steps listed in this section. Open a support ticket with the Microsoft support staff after you’re done. Enter the organisation ID or tenant ID and choose the title “Enable 5-min transaction timeout for Dual Write DV to FinOps Transactions.” The five-minute session time-out window will be enabled for you by Microsoft.
Adding the application to the Azure portal
To create the Microsoft Azure Active Directory (Azure AD) application, follow this approach.
- Select Azure Active Directory > App registrations from the Azure portal once it is open.
- Choose “New Registration,” then fill out the details:
- Name: Type a distinct name here.
- Select a directory from the Azure Active Directory (single or multi-tenant)
- Redirect URI-omit this information.
- Choose to Register.
- You’ll need to remember the application (client) ID value, so write it down.
- For the application, make a symmetric key:
- Choose certificates and secrets from the newly formed application’s menu.
- Choose to create a new client secret.
- Add a description, then indicate the expiration date.
- Choose Save. A key is produced and displayed. For future usage, copy the value.
Give financial and operational apps access to certain features.
To call the finance and operations apps, Dataverse will use the Azure AD application that you developed. As a result, the app needs to be trusted by finance and operations apps and linked to a user account with the necessary privileges. Once you’ve carried out this process, any application that knows the secret of the Azure AD application that you developed will be able to access the dual-write capabilities and call the environment for the finance and operations apps.
- Go to System Administration > Users > Users in the finance and operations apps.
- To create a new user, choose New and fill out the following fields:
- Enter “dataverse integration” or another value for the user ID.
- Enter a different value for the user name field or dataverse integration.
- In this field, select NonAAD.
- Enter dataverse integration or another value for email. The value need not be an active email address
- To add Dataverse, go to System Administration > Setup > Azure Active Directory applications.
- Add a new row and fill it up as follows:
- Client ID: Type in the application (client) ID number that you previously noted.
- Name: Type “Dataverse integration” or another value here.
- User ID: Type in the user ID you earlier created.
- Use the finance and operations apps to log in, then grant the user the System Administrator security role.
The virtual entity data source should be set up.
Giving Dataverse access to the finance and operations instance is the next stage in the procedure. You need a virtual entity data source to finish this step. You are guided through this stage of the process by the steps that follow.
- Go to Virtual Entity Data Sources under Advanced Settings > Administration in Dataverse.
- Choose a financial and operational data source.
Please enter the data from the preceding steps:
- Enter the URL for the app that allows you to access finances and operations.
- Input the URL https://login.windows.net/OAuth.
- Enter your tenant’s ID, for example, contoso.com.
- Enter the Application (client) ID value that you previously noted for the AAD Application ID field.
- Enter the secret that was previously generated in the AAD Application Secret field.
- Type 00000015-0000-0000-c000-000000000000 into the AAD resource box. (This value serves as the representation of finance and operations for the Azure AD application. It ought to remain constant.
- Save your changes.
Stop and restart dual-write maps.
- Log in to the apps for operations and finance.
- Launch the administration page for dual-write.
- Stop the maps, then restart them without first synchronising them.