Developer forum

Forum » Integration » D365 BC Integration odata update and delete? ProductGroup.Name not updated?

D365 BC Integration odata update and delete? ProductGroup.Name not updated?

E-mail notifications
Hans Kloppenborg
Reply
Posted on 09/05/2023 16:25:07

Hello,

We are using the odata v4.0 BC endpoints to import products and prices, but are confused with the Mode settings that are available. 

It seems that the only option to remove records that no longer exist in D365 is to choose Mode "Delete", but its not clear if this just removes records or also updates/inserts new records. It reads as if it does only the delete action. All the other actions say that they do not delete anything, so does this mean that to configure for instance the import for products, where no longer available products must be deleted we would have to configure 2 seperate import steps, 1 to delete, and 1 to insert/update?

Can someone confirm/deny this?

Another issue we have is that the import for the product groups does not update the groupname. We had to remove all groups and re-import them to get the changed names in DW. We checked the endpoint test data, and the values there where correct. The groupname field was present in the mapping, and the import was succesfull. 

Anyone got a hint what could be the matter?

Greets Hans


Replies

 
Rasmus Sanggaard Dynamicweb Employee
Rasmus Sanggaard
Posted on 10/05/2023 10:54:12
Reply
This post has been marked as an answer

Hi,

Delete mode removes missing row in DW but also insert/update rows. 

We have removed this functionality in the new and more generic OData provider and the destination provider has the responsibility (e.g., Ecom Provider -  remove missing rows).

Second question: I assume you are using the older OData provider as destination. This can be a cache issue, have you checked if the name was changed in the database?

Best regards
Rasmus Sanggaard

Votes for this answer: 1
 
Hans Kloppenborg
Posted on 11/05/2023 10:15:28
Reply

Thanks Rasmus,

Yes, we are using the older OData provider as destination, but I was monitoring the data in the database, and nothing changed. Would it be your advice to use the Ecom Provider as destination? When I checked just now it seems we are on version 0.2.28 of de Odata provider, probably because we did an update after starting the project.

N.B. It seems that the how-to article (OData integration (dynamicweb.com)) has disappeared. Do you know if a corrected version will be available soon?

Greets Hans

 
Rasmus Sanggaard Dynamicweb Employee
Rasmus Sanggaard
Posted on 11/05/2023 11:08:38
Reply

Hi,

OData provider 0.2.28 is not the newest version but has the new capabilities. Read more about the differences here: https://doc.dynamicweb.dk/documentation-9/integration/integration-framework/data-integration-activities#sideNavTitle1-2
The choice of which destination provider to use, really depends on what you want to achieve. For products, yes, I would use the Ecom provider as it has a lot of logic related to products and product groups. Read more here: https://doc.dynamicweb.dk/documentation-9/integration/integration-framework/data-integration-activities/ecom-provider
Yes, we will make an updated version of the OData guide and how to work with the new one. You can still find all the information about how the old OData provider works with v4 object types in BC under that provider on doc.  

Best regards
Rasmus Sanggaard 

 

You must be logged in to post in the forum