Developer forum

Hi Carolee,

The API is likely fighting with the data because you can't have 2 orderlines with the same ProductNumber and Quantity and expect them to be distinct. Although this is a ledger, it's using the concept of Carts and Orders. From that point of view, if you were navigating the product catalog and added 1 more quantity to the cart, which orderline would it pick?

To overcome that, you likely need something else to tell Dynamicweb that the orderlines are different from one another. DW's API also looks at the orderlines's UnitId and orderline custom fields to determine uniqueness (i.e. 1 case Wine is different than 1 bottle of Wine, assuming "case" and "bottle" are unitIds).

I can't speak into why it used to work, but sounds like you had some "bad data" before (the perceived duplicate lines) and maybe now that there has been some refactoring of the code making Ledger objects to use similar/same methods as Carts and Orders (because they share much of the same methods and data structure), the data issue has been exposed.

Hope that makes sense and helps you.

Nuno Aguiar

Thanks, Nuno.  Your explanation makes sense... but I don't know of another database (granted my experience is limited) which determines uniqueness by any other means than primary key columns.

To answer your question: If I change the quantity on a line that would be deleted by the platform, the lines are then considered unqiue and neither is deleted.

Thanks again,

Carolee

Hi Nuno,

As we discussed offline, this is an intentional combining of lines but a bug was introduced at some point because the quantities are not being combined, so we still need some help resolving the problem.

Hi Nuno and others,

This remains a problem.

I understand now that combining the lines is intentional, but it's not being done correctly.  The quantity of the lines should be combined, too.  Can this be logged as a bug, or is there some further exploration I need to do?

Thanks!

Carolee

Hi Carolee

Yes, we can look into it.

One issue is correct combination of quantities.

We can also make a setting to not combine lines?

As it is now, if you define an orderline field and give them unique values, that will also keep DW from merging. Might be a workaround for now.

If you have other requests in this regard, please let us know so we can take it into consideration when looking into this.

Sorry about the inconvenience, Nicolai

Hi Carolee,
The issue is because the Dynamicweb Api checks for the orderlines per particular order if they are not doubled.
And the comparison is made on those fields:
ProductId
ProductVariantId
UnitId
ProductNumber
ProductName
DiscountId
RewardId
OrderId
OrderLineType
ParentLineId
OrderLineFieldValues
Bom
Date
Modified
Reference
The problem is because your deleted order lines are considered as a dupluicates since all ot their fields except OrderLineId are equal.
When the deletion happens it writes the information about that into the log in this folder:
/System/Log/Ecom/CartV2/DeletedDoubleOrderLines
Maybe you can somehow change some orderline custom field values or some other column value from the columns list above so your
imported OrderLines are then not cosidered as duplicates and will be then not deleted?
BR, Dmitrij

Hi Nicolai and Dmitriy,

We don't mind orderlines combining and, on other projects, have used the trick of a custom field to force lines to not combine, so I think all we need now is to have the bug addressed to make sure orderline quantity and price fields are combined when the lines combine.

Thanks, guys!

Carolee

Hi both,

Any update on my previous post?  

Thank you!

Hi Carolee

The lines do not combine - duplicates are deleted. We have looked into this and there is no quickfix for this as the logic has to be completely re-written if it has to support combining lines instead  pf removing duplicates - and that would have big implications testing wise since a lot of solutions will potentially be affected, integrated solutions in particular. There are a lot of things to consider if digging into this - discounts, BOMs, giftcards and a swarm of other things that can go wrong. 

The only option right now is to decorate a custom field with something so that your duplicates are not handled as such. Or if they are duplicates, get them merged before sending them in.

I understand that this is not the solution you are looking for.

BR Nicolai

Thanks, Nicolai - I missed that in earlier posts.  We found a solution for Hewitt and are good to go!