{"id":2279,"date":"2021-10-05T10:54:53","date_gmt":"2021-10-05T10:54:53","guid":{"rendered":"https:\/\/devbloglavaprotocols.nityo.in\/set-your-salesforce-my-domain-name-by-winter-22-release\/"},"modified":"2021-10-05T10:54:53","modified_gmt":"2021-10-05T10:54:53","slug":"set-your-salesforce-my-domain-name-by-winter-22-release","status":"publish","type":"post","link":"https:\/\/www.lavaprotocols.com\/the-cloud-blog\/set-your-salesforce-my-domain-name-by-winter-22-release\/","title":{"rendered":"Set your Salesforce My Domain Name by Winter \u201922 Release"},"content":{"rendered":"
<\/div>

We want to make sure you are aware of this change, as well as the potential impact to your Salesforce org so you\u2019re not disrupted when the changes take place.\u00a0<\/p>\n

Detailed information about the upcoming change can be found\u00a0here<\/a>. To get the exact date when the change is effective in your org, navigate to\u00a0Trust Status<\/u><\/a>, search for your instance type, and click the Maintenance tab.<\/p>\n

When deploying your My Domain, we highly recommend that you enable enhanced domains if they\u2019re available for your org. Enhanced domains are the future standard and complete the update to meet browser requirements and will be enforced with the Summer \u201922 release. For more information, see the\u00a0Plan for Salesforce Domain Changes: My Domain and Enhanced Domains<\/u><\/a>\u00a0knowledge article.<\/p>\n

To ask questions about My Domain or Enhanced Domains enablement, visit our monitored\u00a0My Domain and Enhanced Domains<\/u><\/a>\u00a0Trailblazer Community.\u00a0Answers to frequently asked questions are also listed below.<\/p>\n

Kindly ensure that this information is shared with your Salesforce org administrator soonest for them to take the necessary changes covered below.<\/p>\n

<\/p>\n

My Domain Changes Frequently Asked Questions<\/strong><\/u><\/p>\n

What is changing?<\/strong>
To use the latest features and comply with browser requirements, all Salesforce orgs must have a My Domain by Winter \u201922. This change gets enforced via the\u00a0Deploy a My Domain<\/u><\/a>\u00a0release update.<\/p>\n

How will my organization be impacted?<\/strong>
This change applies to all customer orgs that have not deployed a My Domain by Winter \u201922. If a My Domain isn\u2019t deployed in your Salesforce org before the Winter \u201922 release, Salesforce sets one for you based on your org ID. If you prefer to use a different My Domain name than the one assigned, you can change it. See the\u00a0Change Your My Domain Details<\/u><\/a>\u00a0help article for details.<\/p>\n

What actions are required?<\/strong>
Because your My Domain affects all application URLs, we recommend that you test and deploy a My Domain before this change is enforced in the Winter \u201922 release. We also recommend that you test all My Domain changes in a sandbox before updating production.<\/p>\n

To complete this update, follow the testing and activation steps in the\u00a0Deploy a My Domain<\/u><\/a>\u00a0release update located in\u00a0Setup > Release Updates.<\/i>\u00a0For details on how to set up, test, and deploy a My Domain, see\u00a0My Domain<\/u><\/a>\u00a0in Salesforce Help.<\/p>\n

What resources are available to help me prepare for this change?<\/strong><\/span><\/div>\n

\n