Hi Morten

As you found out, the orders are cached by the Customer ID until it expires or it is invalidated.

You can do either of these two options:

1. Save the updated cart for Person B. Then invalidate the cart for Person A, by removing the cache key from the cache (you will have to build the same cache key and then "remove" it from ISynchronizedObjectInstanceCache).
2. Save the updated cart for Person B (set the ID to 0 to force inserting a new cart in the database). Then delete the cart for Person A (by calling IOrderRepository.Delete with the previous ID).

Option 1 corresponds to taking ownership of the cart, as you put it.

Option 2 is more like copying the cart and deleting the original.

But the end result would be the same.

Hi Stefan

Thank you for the answer
Do you know the format of that cache key, or where to find it?

I actually had something like Option 2 in mind as an alternative solution.

Generally you can use the Episerver DeveloperTools add-on to inspect local cache items and then derive patterns of cache keys.

I found this example for you (replace the parts with your own values):

EP:DOR:1311c287-0175-4ba2-979c-d7f07aa1ed14:Default:ICart

• The GUID matches my test Customer ID
• "Default" matches the name of my regular cart instance (this can also be wishlist or a custom cart name in your solution)
• "ICart" seems to refer to the order type

Be aware that this is a derived cache key format. Although I doubt it will suddenly change, there is no guarantee that it won't.

Changing CustomerId is quite unusual thing to do, but it's argubly a bug... I will see if we can do anything about it.

Stefan, you are my hero of the week!

That cache invalidation was the final piece to my puzzle. Now everything works as intended.