For an upcoming POC we have to know what kind of entity-relationship architecture EPiServer Commerce offers.
We are going to import data from a backoffice database and use the EPiServer Commerce API to create/delete/update catalogentries in the Mediachase db.
I already have seen an example of how to create a catalog entry, but I don't know how far the EPiServer Commerce API is going to help me as a developer to perform cascading deletes or create relationships between for instance products and variances.
Is this offered from within the API (like an OR Mapper such as the .NET entity framework is or like nhibernate)?
If so, is there an example of a cascading delete/relationship insert that I can use as a reference?
Maybe this will help:
It comes from:
It shows you how you can add event listeners to the catalogue system (similar to the DataFactory events in CMS). You could use this to create custom handlers to implement your specific business logic.
Hope it helps!
Ok that is also a possbile solution. I was looking for the api to handle this stuff itself (cascading deletes for instance are not handled in the case a contact is deleted => the addresses of the contact still remain in the db). But with handlers it should be possible to implement these constraints yourself in the correct order.