6
You should not use "../utils/utils" for imports from modules. It should be 'c/utils'.
Implementation:
Create utils module:
sfdx force:lightning:component:create --type lwc -n utils -d force-app/main/default/lwc
Delete utils.html file.
Put below code in utils.js:
// mortage.js
const getTermOptions = () => {
return [
{ label: '20 years', ...
4
I believe the problem is the space in FI lwc.
Having white space in the alias name is likely messing up the CLI arguments.
Either take the space out or try wrapping the alias with quotes. I'd probably stick with having no white space in the alias, as it will likely cause issues elsewhere.
4
The SFDX URL can be used to authenticate to the salesforce cli without needing any JWT Token or using browser to key in the credential .
Infact it is the easiest way to authenticate through CLI. Let me explain how salesforce cli authenticates today.
First time when you login via the CLI, you go to salesforce login screen and key in credentials (if you are ...
4
Messaging.renderStoredEmailTemplate does use a SOQL statement. The documentation says:
Executing the renderStoredEmailTemplate method counts toward the SOQL governor limit as one query.
Do not execute this method in a loop, as it counts as a query.
You might consider using setTemplateId instead, which should work for most normal purposes. Usually, one ...
3
Package version creation takes place in a scratch org, whose configuration must meet the minimum requirements for your package's metadata in order for it to be deployed there.
You can specify a scratch org definition to the force:package:version:create command with the -f argument. You'd do something like this:
sfdx force:package:version:create -p assured-...
3
As a background information:
This bug was recently introduced to the VSCode toolbox. Here's a bug report related to this: https://github.com/forcedotcom/salesforcedx-vscode/issues/1635
In order to deploy, right click on the LWC folder in the editor tree and select "SFDX: Deploy Source to Org". Using the deploy on save functionality will fail, since it ...
3
Just got an answer from the support that this is known bug and will be resolved ASAP.
2
You can use source:retrieve command.
Some of them are like:
To refresh and retrieve the files already pulled in source:
sfdx force:source:retrieve -p path/to/source
To retrieve all Apex classes:
sfdx force:source:retrieve -m ApexClass
To retrieve all custom objects and Apex classes:
sfdx force:source:retrieve -m CustomObject,ApexClass
There are many ...
2
you need to create service component (component without *.html file).
Here is the example from documentation.
Your utils file.
// mortage.js
const getTermOptions = () => {
return [
{ label: '20 years', value: 20 },
{ label: '25 years', value: 25 },
];
};
const calculateMonthlyPayment = (principal, years, rate) => {
// ...
2
Lightning Sync is just a name just like Lightning Platform, Lightning Connect and soo on.... It has nothing to do if you use Classic or Lightning.
Check docs, it says it's for both Classic and Lightning
2
You have to specifically name the objects you want, e.g. -m CustomObject:Account,Opportunity
Alternatives I know of:
1) Use this VSCode plugin to easily produce a package.xml by point and click, then retrieve against that.
https://marketplace.visualstudio.com/items?itemName=VignaeshRamA.sfdx-package-xml-generator
2) Use shane-sfdx-plugins which supports ...
2
The metadata components that are not included in the new version are removed from the target environment if they do not have dependencies. If there are dependencies on those components, Salesforce marks them deprecated instead of deleting them.
Metadata that was removed in the new package version is also removed from the target org as part of the upgrade. ...
2
unfortunately setting default values on navigateMixin in LWC is not yet supported:
LWC counterpart to Aura's force:createRecord event
What you can do instead is create an Aurawrapper component to enclose your LWC. then fire a custom event from lwc that will be responded to by the parent Aura, then Aura launches a createRecord event with the passed ...
2
Ok I finally found a solution.
This was an annoying problem since the error message that you get back is quite misleading IMO. The problem is not with your custom objects, or atleast not in my case.
The issue was that you need to enable Quotes for your scratch org and this I did not know.
So for anyone who is facing same kind of issues:
Make sure that you ...
2
The easiest way would be to use the ADK that salesforce ISV team provides for fsc.You can access the open source project here
The best part about ADK is it also has templates that gives you test data for your org.
The other alternative is since FSC publishes package here, you can use the sfdx force:package:install --package=<packageIdofFSC> command ...
1
When you deploy to org select the master folder and then select deploy source to org don't deploy the single file
1
what you're saying is you need to populate a field value (in this case the accountId) with the account record where the button was clicked on. unfortunately setting default values on navigateMixin in LWC is not yet supported:
LWC counterpart to Aura's force:createRecord event
What you can do instead is create an Aurawrapper component to enclose your ...
1
Yes, you can install FSC in a Scratch Org, just as you would in production or a Sandbox, either by the URL or with force:package:install (also this document) from the Salesforce DX CLI. If using unlocked packages, you can also specify dependencies on FSC in your unlocked package to allow the package versions to be created.
1
After you create a self-signed cert in SF, you can export the keypair (private key/public key) as a JKS keystore. You can then extract the private key from the keystore via either keytool (ships with Java runtime) or OpenSSL.
1
From my tests in api version 46 (Summer'19), it seems the procedure described here still works despite sfdx handling flows differently since api version 43.
Find the version numbers of the flow you want to delete by querying FlowDefinitionView
pack them all into your destructiveChanges.xml which will look something like this:
<?xml version="1.0" ...
1
I think the first important distinction to make when using VSCode, and consequently the underlying SFDX CLI, is if you are doing source driven development, org driven development, or change set driven development.
Have a look at the following Trailhead Trail and a specific module:
Trial - Determine Which Application Lifecycle Management Model Is Right for ...
1
On the whole, SFDX doesn't work well with profiles.
If you're using unlocked packages with SFDX to break your system into modules, the problem is that a single profile may need to have permissions relating to many modules. So each package would need to write to the same profile, and they can't all own the profile.
So, the usual approach is to use ...
1
Sandboxes are not, and never have been, designed to support Managed Package development. People did so only because Developer Edition orgs were painful enough to work with and coordinate, that ISVs would rather have used Sandboxes. No longer is this true. Unlike Sandboxes, Scratch Orgs always come as a clean slate. This means no accidental dependencies to ...
1
I work at Salesforce.org, where we created and use the free and open source CumulusCI (CCI) to manage the builds and environment generation for products like the Nonprofit Success Pack.
CCI prescribes "CumulusCI Flow", which is a branching and workflow model specifically designed for building managed packages using SFDX and scratch orgs. (CCI is in essence ...
1
Our developers add features to our managed packages using SFDX and scratch orgs, and our Continuous Integration uses those too via https://claimvantage.github.io/sfdx-jenkins-shared-library/. Scratch orgs support namespaces.
But at the moment, the package version upload is done back in the old developer edition org by doing a:
sfdx force:source:convert
...
1
By default, Apex Compilation is off for Sandbox, Scratch, and Developer Orgs, while it is turned on for Production Orgs. How Apex is executed has been described in several Dreamforce sessions, such as Peek Under the Hood of the New Apex Compiler. It's a rather long watch, but I dare say it'd be insightful.
That said, here goes:
force:package:install --...
1
Look in Setup at the field on My_Custom_Object__c that is a Lookup or Master-Detail to Account. Under Master-Detail Options (or Lookup Options), find the Child Relationship Name. This is what gets suffixed with __r in a parent-to-child query. In this screenshot, the relationship name is Business_Lines:
So a parent-child query would look like:
SELECT Id, ...
1
Your options aren't mutually exclusive. The force:package:version:create command docs say that the command "Creates a package version in the Dev Hub org." But your DevHub org is still on a Salesforce instance, and yes, anyone with the package version id and the installation key could install it. From PM Dileep Burki's unofficial FAQ:
An unlocked package ...
1
DeferSharingCalc is first step to enable Defer Sharing Calculations feature in scratch orgs. For using this feature, User should have Manage Users AND Manage Sharing Calculation Deferral permissions. Create a permission set with these permissions and assign it to user, then you will be able to use this feature in scratch orgs.
1
Now with the latest sfdx update(7.21.0) you can run 'sfdx force:source:deploy' command with specific test classes. Check below command.
sfdx force:source:deploy -p "./PathToMetadata" -l RunSpecifiedTests -r TestClass1,TestClass2 -w 33 --verbose --loglevel fatal
https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_reference.meta/sfdx_cli_reference/...
Only top voted, non community-wiki answers of a minimum length are eligible
