6

Faster time to market is not a preference, its a necessity now a days. SXA is not just about its toolbox and pre-built components. Its about the entire SXA Website Development Process which help you to expedite the website development process. In a non-SXA project you always have dependencies on the previous phase. Most importantly the Content Entry, ...


5

Of course, it is worth it! I will not write down all the features again as it was mentioned thousands of times on different blog posts. It's not just about the components which are shipped with SXA. There are much more features which will speed up your site development process drastically. Just a few articles from first Google results: The Benefits of ...


4

I just received an answer from Sitecore support. You have to reference next dlls: Sitecore.Commerce.Engine.Connect Sitecore.Commerce.ServiceProxy Microsoft.OData.Client To retrieve the sellable item from Sitecore Commerce 9 Update 1 you can use following code snippet. To retrieve a sellable item without variants: var container = Sitecore.Commerce.Engine....


3

To fix this, Verify following are set up correctly Valid SXA licence is present Make sure the host name in /sitecore/content/Sitecore/Storefront/Settings/Site Grouping/Storefront is correctly configured to the web site you are browsing the sitecore in. Make sure the template of the home item is inheriting the home page configuration template.


3

I'm still new to using SXA so take my opinion with a grain of salt. I will provide some examples to explain my position. What I can say is that there are enough benefits to using SXA that I would recommend it but I can't say it's all green grass and rose petals. There's quite a learning curve as it relies a lot on SPE to create many things which aren't ...


3

First of all, try to globally disable asset optimization: You can also disable it per site: If you still want to use ?aodisabled=1 ensure that this "switch" is enabled. Take a look at Sitecore.XA.Foundation.Theming.config configuration file and find XA.Foundation.Theming.AssetsOptimizationSwitch.Enabled setting:


2

You should configure GlobalPhysicalFulfillmentPolicy inside commerce engine services. Do following: Open folder CommerceAuthoring\wwwroot\data\Environments folder. Open environment files e.g. PlugIn.Habitat.CommerceAuthoring-1.0.0.json and PlugIn.Habitat.CommerceShops-1.0.0.json. Search policy "GlobalPhysicalFulfillmentPolicy" inside it and configure the ...


2

So the hierarchy is as follow: SXA requires Sitecore, and Storefront Commerce (CXA) requires SXA. CXA is using SXA as a platform and is using a lot of SXA features. They still have a lot of custom logic like for example usage of Knocout.js and the fact that they are registering their JavaScript filed and Models is related to those custom features. Please ...


2

Sounds like you haven't setup your security for your Tenant/Site, or if you have, the domain is not configured. If you setup your SXA Security and pick a new domain for the tenant or site, it is not automatically added to the Domains.config file. To configure the domain, just click the Domain Manager from the Launch Pad: Then click New and add the domain: ...


2

I'm afraid you'll have to use area's.. Or rename your controllers. To make it less rework, you could plugin a processor that scans assemblies and creates areas on startup. Only thing left to do is to add the area name to your renderings. I've tested this with the code below: public class HelixAreaInitializationProcessor { public virtual void Process(...


2

Since you have tried all the options, the only way to disable optimization of styles and css is to navigate to \App_Config\Modules\SXA\Foundation\Sitecore.XA.Foundation.Theming.config and modify the following value to true and that will let you enable and disable asset optimization switch <setting name="XA.Foundation.Theming.AssetsOptimizationSwitch....


2

Make sure your catalog is not selected in path - /sitecore/Commerce/Catalog Management/Catalogs


2

In all the sitecore 9 and above versions, this error happens when the sitecore instance is not able to find out the correct instance of commerce engine. The storefront will get the configuration from ShopsService URL and communicate with the corresponding commerce engines. Here are 2 steps you must check when this happens Go to showconfig.aspx and find the ...


1

You can use the Model variant definition - that was introduced in SXA 1.7 (don't know what version you are using though) which is compatible with Sitecore 8.2-upd7. With the model variant you can display custom data in a rendering variant. Wrote a blog about last year: https://ggullentops.blogspot.com/2019/03/external-model-data-SXA-variant-Sitecore.html ...


1

This issue was strange, previously I did setup several times Sitecore Commerce Engine 9.2 locally and I did not get this issue. After, cleaning up the previous versions and reinstalling a new Sitecore Commerce Engine 9.2 I did get this issue. However, it was a known issue that Sitecore provided a patch. Download the package, unzip, copy config file and dll ...


1

There's a easier way to do this since you are using 7zip. Extract just the XML file and edit it Drag and drop it back to the 7zip interface. Save the archive and you are done


1

I don't think there already is a Commerce version available for Sitecore 9.1. You can find all compatibilities for Sitecore Experience Commerce here in the compatibility table here: https://kb.sitecore.net/articles/804595


1

Figured out that somehow the catalog details was reset in configuration template. Steps : Open Commerce catalog configuration "/sitecore/content/Sitecore/Storefront/Settings/Commerce/Catalog Configuration" For default instance set value of catalog to Catalog : sitecore/content/Sitecore/Storefront/Home/Catalogs/Habitat_Master For 'Start Navigation ...


1

Solution is 2 step process, 1) Add "Default Commerce Page" Template to base template of the non-SXA pages. 2) Goto standard values --> Goto section Designing --> Select the Page Design


Only top voted, non community-wiki answers of a minimum length are eligible