26 Results for Category Sitecore Platinum Partner


Los Angeles, California, January 14, 2019XCentium, a full service digital consultancy, today announced it has partnered with Avalara (NYSE:AVLR), a leading provider of tax compliance automation software for businesses of all sizes, to offer AvaTax to its customers. This partnership enables Sitecore Commerce™ customers to efficiently achieve tax compliance through XCentium's partnership with Avalara.


There are many mechanisms for monitoring the health of Sitecore, but Heartbeat.aspx is the simplest. It is easy to monitor with third party tools and requires no knowledge of technological underpinnings. With the release of Sitecore 9, however, things have gotten a bit more complicated. Heartbeat checks every database, even unused ones. this can lead to false negatives and problems monitoring site health in different environments. Fortunately, there is a solution!


This post is somewhat of a sequel to my previous one around multi-site and multi-language setup. When there is only one site and only one language things are pretty straightforward in terms of site context. Once multiple sites are introduced every time we are getting an item in Sitecore and/or building a link we need to make sure we do it within the correct site and correct language. For the most part Sitecore does it out of the box but there are cases when this functionality breaks down.


In previous versions of Sitecore Commerce the SQL Database Schema included 2 tables:

CommerceEntities: Stored all Commerce Entities (Catalog Items, Orders, Promotions…) as JSON.-CommerceLists: Maps Entities to Lists (SellableItems To Category for example).

Those tables quickly reached a huge amount of Data and caused significant performance issues in some cases.

To solve that, Sitecore Commerce 9 introduced a simple SQL Sharding technique driven by an Environment JSON Policy-Set: PlugIn.SQL.Sharding.PolicySet-1.0.0.json


As a website evolves and its audience grows making your content available in multiple languages becomes a top priority. The most common way to achieve this goal is to use Sitecore's out of the box language versioning functionality where the tree is shared and the same item in can have translated versions. But what if it's not only your content that differs between various country sites but also presentation? What if your sites intended for various countries are independent from each other and possibly share some components but not all? What you can do is set up a site in such a way that tree is split between countries meaning each site has its own site definition with its own hierarchy.


SEARCH ARTICLES