...
| Tip |
|---|
Remember you can just use the UP key to re-type the same command again in the CLI terminal. And use UP UP to get to the next most recent command, and keep on going back further in your commands list. (Thanks to first learning about enterprise computing on Unix boxes for that trick). |
Issues
I had an issue where the pull command gave me the following error.
...
But nope, it was not even that. I had not closed VS Code down, I just re-opened it, but even doing a force:source:pull it says I was not in a SFDX project. Yet my path on my terminal was set exactly to the project I was happily working in yesterday. It’s these little things that annoy just trying to get everything up and running to work. OK, this stack exchange post seemed to get me back on the right track… so it looks like it’s an issue with starting from the Trailhead project. I just changed the directory to the dreamhouse-sfdx directory and it worked from there. It’s Weird because I was not in that directory yesterday.
Data Export and Import
Now we need to export some data… to save it to our Source… now of course I have gone and made it more complex and gone beyond the bounds of the stupidly simple examples that Salesforce give on their blog.
...
To understand how the data import works it’s a good idea to understand how the Composite APIs work. as the reference values are similar.
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).
...