Recently the Salesforce team at XCentium ran into case of “database history”. A legacy system we integrated with predated most modern RDBMS’s, and proved to have some interesting challenges.
One of these challenges is the subject of this blog post. To understand the issue, we have to go back a few years.
Sitecore Experience Commerce 9 (XC9) comes with two default environments - Habitat and AdventureWorks. In this post, I will describe how you can safely remove these environments, create new environments and how to remove the sample projects from Sitecore Commerce Engine SDK.
When you are starting on a new project, the Sitecore Commerce Engine SDK gives a good headstart with all the sample projects. Eventually, you will need to remove these sample projects and keep only the ones that are needed for the project.
CloudCraze (CC), the Salesforce B2B Commerce Cloud offering, allows the creation of customer specific pricing using accounts groups and Price Lists. An account group, as the name implies, is a construct that groups Salesforce accounts. An account group has the advantage of being associated to many pricelists. In this manner it becomes possible to allow a group of customers to use one price list and another group to use an entirely different price list. In addition, there is nothing preventing the setup of an account group for just one single customer. This structure provides a broad array of possible configurations. For an illustration of how this works, please check out my blog.
With Sitcore 9 comes a whole new world in topology. Sitecore 9 marks a shift toward a microservice architecture, which affords new challenges and considerations in designing a Highly Available solution that can support Hyper-scale and load.
Installing Sitecore 9 on your local dev machine took some work, but you managed to do it. Now it's time to upgrade your actual servers and solution. Here are some common issues you can run into when upgrading to Sitecore 9.