15
votes
How to install managed package using Salesforce DX CLI?
To install a First Generation Managed Package via sfdx, you do it the same way you do it with the metadata API. The command looks like this:
sfdx force:mdapi:deploy -d packages
The packages folder ...
12
votes
How to install managed package using Salesforce DX CLI?
Have you tried using:
sfdx force:package:install -i 04t6A0000004eytQAA
Docs for this are found in the CLI command reference.
The only thing is that you'd need to know the ID of the package to pass ...
12
votes
Accepted
Friction-free process to switch to SalesforceDX with existing managed package
Summary The next generation of packaging is still very much a work in progress. The core focus is embracing the source control driven
approach of DX into how we develop and distribute packages. The
...
11
votes
Accepted
How to install managed package using Salesforce DX CLI?
This helped me get the right id for app exchange packages currently installed in my devhub:
$ sfdx force:package:installed:list -u [DevHubAlias]
=== Installed Package Versions [2]
ID ...
9
votes
Accepted
How do Salesforce Developers using Visual Studio Code use Github?
This is going to be a pretty quick summary of a very broad area. I am happy to focus this answer more finely on a specific area if you'd like to push me in one direction or another
Source Model
It ...
9
votes
Accepted
SFDX: how can I use a GitHub action script to deploy ONLY what was changed instead of ALL the metadata?
You need to use either sfdx-git-delta https://github.com/scolladon/sfdx-git-delta
Tool to create a dynamic package before running deployment or validation.
You can even create one yourself by using ...
8
votes
Accepted
Salesforce with Git
Do we need to work each developer in a different dev environment? if not, is there any way to work in the same environment without step on each other's toes?
When developers work in the same org, ...
7
votes
Deploy incremental changes using Github and Jenkins
There are a bunch of third party solutions offering native CI for Salesforce. Full disclosure that I lead one of the companies building one but I'll provide you with all options so you can investigate....
7
votes
Accepted
Should the .sfdx or any of its sub-folder and/or files be added to the .gitignore?
You certainly want to gitignore the .sfdx folder. This folder contains information regarding deployment statusses from your computer to your scratch orgs. There is nothing in there that benefits from ...
5
votes
Accepted
Development Life Cycle of using GIT in salesforce.
The "full package" of Salesforce development should include the following features:
Continuous Integration
To ease migration, consider a CI solution. This allows developers to stage/unstage code ...
4
votes
Email html body to plain text body
Use the String function stripHtmlTags() and it will do the work for you.
String1.stripHtmlTags()
4
votes
Git unable to update URL base
I'm not really sure how your repo got into this state, but you have two remotes (server repos to which you can push changes from your repo) configured, and one of them (upstream) has the wrong URL.
...
4
votes
Accepted
GitHub Conflict Resolution issue
What is this file?
Internal housekeeping files that should not concern you (and that you should never intentionally modify).
Did I screw something up that created the conflicts?
You ...
4
votes
Merge Branch || git diff not including .gitignore files
What I feel like is you are doing something wrong from the very beginning. You should include only the files you are interested in in your git repository and branch that to make the feature branch.
...
4
votes
Accepted
Partner Developer Org best practices - how to mirror namespace among PDOs
First, please verify this is the best practices org setup for ISV partners
No, Scratch Orgs, not Partner Developer Edition Orgs, are the best practices in the current development model. Yes, each ...
4
votes
Accepted
Is it possible to link a namespace frome a developer org to a developer hub
It's important to note that linking a namespace does not imply anything about ownership of packages and package versions that use that namespace.
You can link your namespace to an arbitrary number of ...
4
votes
Should the .sfdx or any of its sub-folder and/or files be added to the .gitignore?
The .sfdx folder should never be tracked. In fact syncing would cause a huge issue for rest of the team cloning your project to their local machine, as it may potentially mess up source tracking of ...
4
votes
Accepted
Github Workflow for Package Development
Disclosure: I am on the CumulusCI team at Salesforce.org.
This is CumulusCI's raison d'etre. We've built CumulusCI for years to support building managed packages in GitHub. I completely understand ...
3
votes
Working with GIT and org code in VS code for a single sandbox
There could be multiple use cases for introducing a source code repository into your Salesforce development process.
Metadata backup
You could create backups of your metadata at regular intervals in ...
3
votes
One VCS repo per "artifact"?
On our ISV project we use "NVIE" git branches
https://nvie.com/posts/a-successful-git-branching-model/
So one repo , but multiple branches :)
We also have one SFDX Project ( folder ) by "artifact"
...
3
votes
Deploy incremental changes using Github and Jenkins
Its very late to answer but here is my setup which works:
Code Merged -> Create a deploy folder -> checkout the target branch in workspace - > Merge the current branch to target branch (no commit)-> ...
3
votes
Accepted
Push process builder to gitHub
You will need to include the metadata.
Process Builder metadata can be found under the type: Flow
Read this : https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/...
2
votes
Accepted
Getting Community Page into MavensMate & GitHub
Lightning Pages for community is still not exposed for packaging .You will able to pull it for lightning App Builder but not for community builder pages .
You will need to wait for few weeks(probably ...
2
votes
How to link Salesforce Mavensmate project to Github as one branch per sandbox
What you can do is using a separate folder for your git folder. And for each org(sandbox) you can have a separate Mavensmate folder. You can use a integration plugin to sync between those folders. ...
2
votes
Accepted
Deploy incremental changes using Github and Jenkins
Process that we finally implemented in Jenkins
Source Code Management
Connect to your git repository
Execute shell
Script will get the previous commit (last one that is deployed) from a file and ...
2
votes
Accepted
One VCS repo per "artifact"?
Andrew Fawcett has provided us with an open source demo you can clone and peruse.
Generally speaking, all of the artifacts related to your application should exist in one repo. This allows you to ...
2
votes
GitHub Conflict Resolution issue
Generally, this file (and everything under .sfdx) should not be under source control, as it's a bookkeeping artifact used by SFDX rather than a component of your application. In this case, it's ...
2
votes
Accepted
Setting up Project For Salesforce DX
It doesn't look like you have git installed on your computer. Here's a link to the installation steps: https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
2
votes
How to upload to gitlab repo?
This is git's way of letting you know the history of changes in your local (VS Code) and remote (Gitlab) are different and it doesn't know how to relate them.
This provides a nice background to ...
2
votes
Partner Developer Org best practices - how to mirror namespace among PDOs
As the other answer says you should be using the Scratch org for development and upon merging the changes from different branches you will create a new scratch org (automate this) and push and compile ...
Only top scored, non community-wiki answers of a minimum length are eligible
Related Tags
github × 75salesforcedx × 26
git × 24
deployment × 10
salesforcedx-cli × 7
apex × 6
version-control × 6
mavensmate × 5
ci × 5
github-actions × 5
bestpractice × 4
unlocked-package × 4
managed-package × 3
isv × 3
eclipse × 3
heroku × 3
unmanaged-package × 3
continuous-integration × 3
versioning × 3
cicd × 3
sourcecontrol × 3
error × 2
scratch-org × 2
vs-code × 2
ant × 2