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. 

 

 

 

Labels:

Comments

Post a Comment

Popular posts from this blog

High CPU to completely normal CPU - SXA issue, SXA pages not loading in mobile device

  Hi Team, Today i am going to share one of the nightmarish issue with you all, We are having Sitecore 9.1.1 hosted in azure PaaS environment Our site was working just fine and no noise, but we have been working on a feature release where 7-8 months of development needed to be released to production, Big GO LIVE event right?  Also to make the development smoother we also introduced BLUE/GREEN deployment slots in the same release, so we can easily SWAP slots and go live Everything went well, we went live, we even did load and performance testing on our staging and pre-prod and we were confident enough of results Very next day we started getting "SITE DOWN" alerts, and also product owners and clients mentioned that site is very slow for them in US time and in our morning when we were accessing it, it was working lighting fast so we were clue less at start, but we started digging  1) First thing caught our eyes were HIGH CPU spikes, in US time, also without any traffic CPU u...
3 comments
Read more

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...
Post a Comment
Read more

An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.

You have noticed many times that everything was working fine and suddenly the below error starts coming and you find no way to work it out An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. The reason for this is the receiving size of WCF service is smaller then the data which is coming from service It was working before because it was small,So you will have to try to increase the receiving setting in your end point,Possible settings can be following maxStringContentLength="2147483647" maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" maxArrayLength="2147483647" That would definately help you!!!
1 comment
Read more