So, this problem can be confusing, and I wanted to share the simple solution.
Let's assume the source sandbox is called "uat", and the cloned sandbox is called "uatclone".
Go to the source sandbox and find the user you want to log in using username/pw. If the username is:
The cloned sandbox username will be:
The password in the cloned sandbox will be the same as the source sandbox. Of course, the user must exist in the source sandbox at the time of the cloning, or this will not work.
Special Note: You may want to change your password before the clone in the source sandbox in case there is some sort of password restriction that is being
enforced in the clone, and you have an SSO that's getting around that.
Update -- Since this is being downvoted and challenged by the OP, I want to demonstrate with screenshots.
During sandbox creation, the newly created sandbox will manipulate the second suffix. So, if your username is:
your cloned sandbox would yield:
- First, I check my username in the SOURCE sandbox which in this case is UAT. Notice it ends in .uat - so assume the username is: [email protected]
- Then, I made a sandbox as shown in the "Copied From" column (last one) from our UAT:
NOW FOR THE CONFUSING PART. Which is why this question exists! When I click the "Log In" link shown in the screenshot from PROD, Salesforce will incorrectly assume the sandbox was copied from PROD. However, as shown above it was copied from UAT. Some production usernames in our org have a suffix of .prod (bad practice imo), and the cloned sandbox assumes my username is [email protected] . For me, I cannot log in to this sandbox at all with this username.
Recall Step 1. I checked my username in the SOURCE sandbox. Now, let's try to log in with the convention I suggest... which is [email protected] IT WORKS! Now, lets check what my actual username is to verify:
- Also, I checked other usernames that end with .uat in the source sandbox and have confirmed they also have the same convention [email protected] . I also created a listview to see if ANY username had .prod in it.
- Na da.
Point is it appears to manipulate the second suffix beyond the sandbox name.
As a side note we are not on Hyperforce, but we are on Spring '24 API version 60.