web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Supply chain | Supply Chain Management, Commerce
Unanswered

Dual write: Products from D365 Sales to F&O

(0) ShareShare
ReportReport
Posted on by 35

Hello everyone,

for our client, the architecture of the solution that we are going to implement requires to export the products from D365 Sales to F&O.

To do that, I customized the standard "Released products V2" map, changing the synch direction for all the fields (by standard is F&O > Dataverse, I set the opposite), and I created a whole new map, connecting the F&O entity "Products V2" with the "Global products" table of D365 Sales.

The two maps are running OK, I did not receive any validation errors from F&O, and yet I am creating products in D365 Sales (successfully, no errors are given), but nothing happens in F&O, as if the data is not exchanged and the maps are not "feeded".

Has any of you had experience in such way of integration?
Am I missing something from the Dual Write maps standpoint?

Screenshot from the Released products map:

pastedimage1633420465220v1.png

Screenshot of the Products V2 map:

pastedimage1633420507716v2.png

I have the same question (0)
  • Gian Carlo Profile Picture
    35 on at

    So I was eventually able to synchronise the Products V2 map, and I am now able to successfully export a product from D365 Sales to F&O.

    I reviewed many times the map for the Released products V2 and I believe I am close to get the work done but I am stuck at the error:

    "Unable to write to Finance and Operations apps due to following error(s): {"Write failed for entity Released products V2 with unknown exception - Invalid argument."} Please rectify your data and try again. If issue persists after multiple retries, please contact your system administrator."

    Code d'erreur : 0x80040265

    ID de session : db45abca-791d-437f-80a4-489f4cdbaf77

    ID d'activité : 29aca00c-2115-4123-9237-76379dd3fd58

    Heure : Tue Oct 05 2021 18:06:32 GMT+0200 (Central European Summer Time)

    I get this error when I am trying to create a released product in D365 Sales. If I understand correctly the dual write architecture, at that moment Sales is trying to write through OData, based on the "Released products V2" map, the record of the new released product in F&O, but it cannot because of the "Invalid argument" error.

    I uploaded the error details. Has any of you an idea of what is causing the error? What is it the "invalid argument"? I reviewed many times the source data and the defaults in my map but everything seems to be there: COMPANYID, ITEMNUMBER, PRODUCTNUMBER, PRODUCTTYPE, PRODUCTSUBTYPE, even not mandatory info such as ITEMGROUP, ITEMMODELGROUP, STORAGEDIMENSIONGROUP, TRACKINGDIMENSIONGROUP, SALESPRICE


    ErrorDetails-_2800_7_2900_.txt

  • WillWU Profile Picture
    22,363 on at

    Hi partner,

    This error occurs if the products do not exist in D365FO.

    Please check if products are there in system. You can use Products entity to import products data, then you will use the 'Released Products' entity.

  • Gian Carlo Profile Picture
    35 on at

    Thanks,

    I was eventually able to export both a product and a released product from Dataverse to F&O, I had to adjust the mapping in the dual write maps

  • Biswa88 Profile Picture
    50 on at

    Hello Carlo,

    Thanks for sharing your experience here, really helpful.

    we are trying to synch product data from D365 sales to D365 F&O. We used only one mapping 'Released product creation v2' , ran the map, but no product synchronized though 365 sales has good number of valid products. We even did not get any errors. From your post above, do we need to create two different maps and use those - Products V2 and released products v2? Is there any reason for that?

    Thanks in advance.

  • Gian Carlo Profile Picture
    35 on at

    Hello Biswa88,

    I used two maps because as you know, to create a released product in F&O, you must first create the product: the first map (entity F&O = Products V2, entity Dataverse = Global products) is responsible for the creation of the product, while the second map (entity F&O = Released product V2, entity Dataverse = Shared products) creates the released product.

    That said, I honestly do not know how the Released product creation entity in F&O works.

    If the standard logic behind that entity creates the Product before creating the Released product itself, it would make sense to try and use just one map, otherwise my suggestion is to use two maps, one for the products, one for the released products

  • Biswa88 Profile Picture
    50 on at

    Thank you for the quick response. We will try with 2 maps and update here. Also, do we need to carry out any other checks or steps such as any configurations etc. in F&O?

  • Biswa88 Profile Picture
    50 on at

    Also, you mentioned you had to adjust some mappings in the released product v2 mapping. What are those adjustments please?

    Thanks in advance

  • Gian Carlo Profile Picture
    35 on at

    Products_2B00_ReleasedProductsDualWriteMaps.docx

    Please find attached the maps that we are using. Note that our business scenario is quite simple, all the products that we are importing from Dynamics Sales are service items and they all share basic properties such as Item model group, Item group, storage dimension group, tracking dimension group: this is why we have so many defaults value in both maps.

  • Biswa88 Profile Picture
    50 on at

    Thank you again. We will also have simple service items, so I am expecting similar mappings. Let me try and get back to you.

    Thanks.

  • Biswa88 Profile Picture
    50 on at

    Hi Carlo,

    we are still unable to bring any product data from CE (dataverse), even if we followed the 2 mappings and started a new map for product v2 from scratch. we did not get any mapping error nor anything in the activity log, all good there. The map run successfully but no data imported.

    So I suspect we are looking at the wrong tables in CE/dataverse to source the product data. We first tried the msdyn_globalproducts table- no mapping error, but no product import. However, when we tried to source from the products table, we got a mapping error of 'integration key'. I understand the product number in the products table of data verse is the concatenation of company and product number, but we don't have a field/column to map in the F&O side for the company name in the product v2 entity.

    Could you please help? What can be the challenge here?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > Supply chain | Supply Chain Management, Commerce

#1
Mallesh Deshapaga Profile Picture

Mallesh Deshapaga 254

#2
Laurens vd Tang Profile Picture

Laurens vd Tang 188 Super User 2026 Season 1

#3
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 131 Super User 2026 Season 1

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans