I am doing some experimenting with Synapse Links for Dataverse and to do that I need my FnO data in Dataverse. The way I do it, is using Dualwrite. When I try to sync Sales Order Lines V2 to salesorderdetails I get the following error:
Reason: Bad Request, Header x-ms-client-request-id f1004256-8a98-42fe-86a9-02b8e64a81a9, Produkten kan inte läggas till eftersom den inte är aktiv
(for those of you, not fluent in Swedish it says “The product cannot be added because it is not active)
This means that the product is synced but it is not active. To activate the product it needs to be published. To do this go through the following steps:
In Sales open products
Select a product and click Publish
The problem was I had a couple of thousand products. So I googled and found this forum thread helping me to write a workflow to automate it (this is way beyond my knowledge in CRM).
Yesterday I looked into an issue for one of my customers. In one of their environments they where not able to activate Data Events for any of their entities. The Activate button was completely grayed out and the “Active Data Events” and “Inactive Data Events” tabs did not exist
This is an environment where we are currently running a PoC for DualWrite so I just “assumed” that I had configured PowerPlatform correctly (you know what we say about assumptions)
Turns out I had not followed my own advice and done the PowerPlatform configuration from LCS… Instead I did the linking from within FnO, in the DataManagement workspace.
The solution was to go through the linking wizard in LCS and then the tabs showed up
Note that the change to the Business Events Screen is not instant… I had to have it sitting over night to have the tabs show up
I just set up the CDMUtil for a customer to let them access Dynamics 365 for Finance and Operations Data, exported to a DataLake, through a serverless instance in Synapse. The customer had added a new user and got an error which vas not perfectly logical
Msg 15151, Level 16, State 1, Procedure CustTable, Line 1 [Batch Start Line 0]
Cannot find the CREDENTIAL 'dynamics365_financeandoperations_XXXXXXXX_sandbox', because it does not exist or you do not have permission.
Msg 4413, Level 16, State 1, Line 223
Could not use view or function 'dbo.CustTable' because of binding errors.
The issue was obiously a permission issue… but where??
When we added an earlier user we set up a Role in SQL that had read access to the SQL DataBase. When we added the user to that role it started working… The confusing part was that the error message did not mention the new user anywhere.
When you set up the Synapse connection to Data Lake and FnO… Make sure you add the correct permissions to new SQL-Native users using TSQL in Management Studio.
Back in 2018 I wrote an article on how to configure a D365FO instance to enable the Warehousing App. A lot of time has passed and tonight I will set up the all new and improved Warehouse App so I thought I would also take the time to update the original article
Go to the azure portal. In Azure Active Directory – App Registrations create a web application for the warehouse portal Name: WhatEverYouWant Who can use thisapplication or access this API: Accounts in this organizational directory only Application Type: Web app/API Sign-on URL: https://[theURLforyourdynamicsinstance]/oauth
Open the application to edit it
Verify Application ID. Save this for later…
Go to API Permissions and click Add a permission
Select the API called Microsoft Dynamics ERP (Microsoft.ERP)
Choose Delegated Permissions
Under Permission to other applications click add application and add Microsoft Dynamics ERP
Add the following permissions – Access Dynamics AX online as organization users – Access Dynamics AX data – Access Dynamics AX Custom Service Click Add Permissions
Click Grant admin consent for [Your Organization] and confirm your choice
Go to Certificates and Secrets and click New client secret. Select an expiration and give the key a description like D365FO Warehousing App
Log into Dynamics 365 for Operations and go to System Administration – Users and create a new user (in my case called WMAPP. The email address can be anything since it will never be used. The user needs this role: – Warehouse mobile device user
Now we need to associate the user to the AD Application which is done on System Administration – Setup – Azure Active Directory applications. Here we paste the App ID/ClientID from before and select the user we created. Click Save and you are done.
Install the App from app store and enter these settings: 1. Azure Active Directory ID: AppID/ClientID from step 3 2. Azure Active Directory Client Secret: The key from step 10 3. Azure Active Directory Resource: Your Dynamics 365 URL 4. Azure Active Directory Tennant: https://login.windows.net/yourAzureADtennant.onmicrosoft.com 5. Company: Dynamics 365 for Operations Legal Entity
To configure the mobile att you create a JSON file with the connection setting