Skip to main content

ERROR: DoCommand Failed:Invalid or missing value for property 'Domain'

 Hello Folks,

Its Sunday evening and i am in my balcony planning to publish few blogs (which are in my drafts from long time) before this Sunday is over :) So today i wanted to share quick info on one of the issue we were running into while creating a user on commerce side 

Scenario

So, Here is a thing, we were implementing custom domains for our client for their multi site tenant setup, so they have one instance for US, one for Canada likewise and they wanted a user creation to be in that domain 

Now our storefronts already had proper domain mapped on sitecore side like following 

  

But as soon as we were trying to create a user from storefront using OOTB registration component, it was giving below exception 

972 01:47:16 ERROR DoCommand Failed:Invalid or missing value for property 'Domain'.

972 01:47:16 INFO  AUDIT (DemoUS\Anonymous): Add user to role: DemoUS\Extranet User, user: DemoUS\test1@test.com

972 01:47:16 ERROR Invalid or missing value for property 'Domain'.

972 01:47:16 ERROR User created but external Id was not provided.

 

Now looking at the exception it was time to look into commerce side as we have seen before that while creating a customer it needs a domain, now because for a custom domain, existing OOTB json files of domains will not have that domain and because of that, from sitecore when code run it tries to find that domain which is used while creating a user and it is not able to find it, so simple solution to this is to add that domain to existing list of domains which are available in commerce.

 

Solution

Now on authoring environment you will find different environment configuration file, in our case we already had our custom environment bootstrapped, so it was referring to our custom environment files, Click Here to read how to create custom environments

 

So What is needed is to open respective environment files json files and add our specific domains there, like below 


1) Go to \CommerceAuthoring_local.ce\wwwroot\data\Environments on your respective roles (i am taking example of authoring here)

2) Find "domain" in the file and add your custom domain, like following 

 

 

3) Now make sure to run bootstrap to allow changes to be applied and now make sure that you are able to see this domain on customer object while you are creating a customer on commerce side like following 

 

 

 

 

And you should be good to go, next time you create a user it should also create a customer too with that custom domain :) 

 

TIP: This is only applicable if you are using SXA and commerce flow, if you are using commerce in headless environment, you will get the same exception but solution is totally different for that, Read Here the solution written by one of my colleague "Aakash Savalagi" for it 

 

Happy Sunday and good night. 

 

 

 

Comments

Popular posts from this blog

Set up leprechaun code generation with Sitecore XM Cloud Starterkit

Hi Sitecorians, It has been amazing learning year so far and with the change in technology and shift of the focus on frontend frameworks and composable products, it has been market demand to keep learning and exploring new things. Reasons behind this blog Today's topic is something that was in my draft from April-May, and I always thought that there is already a good documentation out there for  Leprechaun  and a blog post is not needed, Until I realized that there was so many of us facing same kind of issues and same kind of problems and spending same amount of time, That is where I thought, if I could write something which can reduce that repetitive troubleshooting time, That would really help the community. 1)  In a project environment, if we get into some configuration issues, we resolve them, we make sure we are not blocked and continue, but if you think same issue, same step and same scenario will come to other people, so if we can draft it online, it will help othe...

Every Sitecore Instance using GQL is prone to this scenario of template not found - Sitecore Component With GQL Queries Broke On Production

Hello Team, Today, I wanted to share a real scenario and a solution of it about what happened  suddenly to our components and how we identified it and how we resolved it, and most importantly it could happen to your installations too Scenario We have one Sitecore 10.2 headless instance and two sites, One site is non-sxa which is legacy site and another site is a new site which uses headless SXA. Now, non-sxa site is already live and working fine with all components etc. and the new headless site was in development and it has separate development team, So we have same DEV/UAT/PROD environments. One fine morning they took their code and site on environment but strangely some of the GQL components like header footer of legacy site disappeared.  Troubleshooting Steps 1) We checked the broken component's GQL query  2) We took that query and fired it in GQL IDE, and we observed that, Some of the templates references we used were not found, which was working just fine and we hav...

401.1 Unauthorized with windows authentication error code 0xc000006d

How many of you have faced this hosting issue when you do everything what it takes to run the site with windows authentication but still you are getting the same error again and again? If you think you also have faced the same issue and you tired of reading MSDN KBs for it and still have not found the issue (If KB has solved the issue, well and good, if not you can try this trick),Please Read below Typical scenario In typical hosting with IIS, i did every possible things like enabling windows authentication, changing it in web.config, configuring connection pool, authorization rules, it asks me for window authentication login and despite of entering correct credentials it always fails and keeps on asking for login, and when pressed cancel it gives 401.1 with 0xc000006d error code Solution (Which worked for me at-least after trying for almost 6-9 hrs) You need to change the Loop Back Check in registry so that it allows the host names which you are giving in url are allowed and au...