...
| Info |
|---|
hmm, error.
Even though I’m within the dates of the preview as specified here https://developer.salesforce.com/docs/atlas.en-us.220.0.sfdx_dev.meta/sfdx_dev/sfdx_dev_scratch_orgs_version_selection.htm |
| Tip |
|---|
This is fixed now! (As of 10-Jan) So try again! |
So I start again without the Preview Org and run the command and I have a scratch org.
...
Interestingly I had to use Sandbox as my OAuth endpoint to login. I thought Developer Orgs were “Production” orgs - maybe scratch orgs are different or maybe because I am using my production org as the Dev Hub. Dunno.
Re-Creating the Scratch Org
So the whole point of the Scratch Org is to re-create it from Source.
Now that the preview error is sorted, I have a preview developer org.
| Tip |
|---|
Let that sink in! A preview developer org. We haven’t been able to have those before. Pre-release orgs, yes, but developer orgs, no. |
So I do
| Code Block |
|---|
sfdx force:source:push |
And I get the dreaded message <unknown> duplicates value on record with id: <unknown>. This is where the time sink starts. How does a company the size of Salesforce allow an error of that level of bullshit even get out. It’s even worse than a Gack!
Plus I’ve got some flow errors that are related to new flow features that I’m not even using. (Similar to this but I’m not using a Scheduled Flow or a Start Node).
Trying to work this out:
Disable field tracking on the one object that has it
Put my flows into .forceignore (that didn’t work).
Disable field tracking on the two fields that have it.
Delete flows completely (they are still in my git).
Hmm, that worked. Weird.
Revert my flows
Nope, same error.
So there is an error with Flows. I don’t want to have to re-create my whole 4 flows again, since flows are the basis of my demo!
Weird Things
The end goal for me would be to create a scratch org that I am happy using that has all my standard modifications in it (eg as shown in New Salesforce Org).
...