New answers tagged

3

The list is available in the Metadata Coverage Report: https://developer.salesforce.com/docs/metadata-coverage However, Field Level Security is not part of the field or object itself, but part of the Profile or Permission Set where the FLS was added. So you'll have to add this metadata to your package too if you want to deploy the access.field


0

Following answer came from the SF-Support: I have had a discussion with the internal teams here. Based on what we checked, It seems that the error you are seeing is expected since the topicsForSobject is not available under the documentation. https://developer.salesforce.com/docs/atlas.en-us.packagingGuide.meta/packagingGuide/...


0

The manifest option currently deploys an entire object, presumably because it's basically a wrapper for the mdapi. Use the source-path option instead. sfdx force:source:deploy -p force-app/main/default/objects/Contact/webLinks/


1

We found the issue. Someone had added the flows folder to the forceignore file in VS CODE thats why we were not able to deploy to any of our sandboxes. This problem is now resolved.


0

I had similar issue. Pay attention to uppercase/lowercase. I see you have key={fields.id} in your html. Change to key={fields.Id} Even if your SOQL mentions "Select ID, whatever ...from " in the front end and js it has to be Id not ID or id


0

Please verify that you have Account.object xml file in your Source pulled from Production. When you pull Standard object, you have to specify them explicitly: sfdx force:source:retrieve -m CustomObject:Account or by Ant <types> <members> Account </members> <name> CustomObject </name> </types> So if you use just <...


3

Can you post the code? When iterating through a collection for rendering lists the unique id key is required. Sample below; <!-- helloForEach.html --> <template> <lightning-card title="HelloForEach" icon-name="custom:custom14"> <ul class="slds-m-around_medium"> <template for:each={contacts} for:item="...


0

Add managed package subscriber id as a dependency in json.


1

For anyone struggling with the same above mentioned error while creating scratch org, I was able to create scratch org by downgrading my salesforcedx plugin version to : salesforcedx 47.18.0 (47.18.0) instead of latest at this moment(salesforcedx 48.5.1) sfdx plugins:install salesforcedx@47.18.0


0

At work we have a plugin hosted on a private npm registry and are using GitLab for source control. After trying many different things, I found that providing the url is the best practice for installing private plugins: sfdx plugins:install https://your-git-whatever.com/namespace/project-name.git Doing it this way will allow you to run sfdx update and it ...


2

No. It is not currently possible to rename or delete an unlocked package or package version. You will want to vote for this Idea. In the meantime, the best you can do is deprecate the package so it cannot be installed.


1

So from some investigation I have solved it, Salesforce documentation fails to mention this and it seems to only apply to double quotes but when using them to transmit data in there format (i.e sfdx force:data:record:create) you need to surround the value in single quotes. This is a missing detail to there documentation that says you only need them if spaces ...


2

Fortunately, there is an easier way to do this. I often use this while writing apex unit tests. As mentioned in the comment by Kris, you can run specific or all test class methods from a class using the VS code. To be able to see the code highlighted, you need to do enable it from the VS code bottom toolbar. When you have that checked, you will be able to ...


2

After searching I got to know that there were no plugins installed in the Salesforce CLI sfdx plugins:install salesforcedx@latest I ran the above command in the Command prompt and installed the latest salesforcedx plugins. after this, I was able to create a salesforce project successfully.


1

I finally ended up reinstalling vscode. Uninstalling VS Code doesnt remove the extension folders. I went ahead and deleted all the folders related to salesforce in the extensions folder and then opened VS Code and reinstalled the salesforce extensions as well. Everything is back to working condition.


1

Those elements are still "bundled" in this release (7.50) of DX (and all prior versions). To extract them, use the Workflow object: <types> <members>*</members> <name>Workflow</name> </types> You'll have files in the folder workflows, named after the object for which the metadata pertains to (e.g. Account....


1

Selenium Action does the trick and can type to the console: Actions actions = new Actions(webDriver); By linesBy = By.xpath("//*[@class='CodeMirror-code']//pre/span"); List<WebElement> lines = webDriver.findElements(linesBy); while (lines.size() > 0) {//deleting old Apex code lines.get(0).click(); actions.sendKeys(lines.get(0),...


0

force:data:tree:import always creates new records. You can't insert Profile objects. As such, that won't work. You can import such records, but not with this tool. You'll need to use force:data:bulk:upsert. Note that you won't be able to fully automate this anyways (using only dx), because usernames still need to be unique in each org. You need a script to ...


1

As far with the tests I made the org just pulls the changes you did or the metadatas you explicity put in the package. If you want to get everything whithin the Object you should get all CustomFields, all Actions, etc. and the Object you want, for example. <types> <members>*</members> <name>CustomField</name> </...


0

Please update the salesforce latest plugins with the below command. This issue is resolved in latest release. I have faced same problem, I fixed it with below cammand. sfdx plugins:install salesforcedx@latest


0

Here is what I did to locate the problem after going through the discussion in this issue: https://github.com/forcedotcom/cli/issues/94 Created a new folder named force-app1 and updated force-app in sfdx-project.json to force-app1 Copied entire main folder from force-app to force-app1 Tried the command sfdx force:source:convert -p force-app1 -d test and ...


1

You could use the auth command from the sfpowerkit plugin: sfpowerkit auth:login https://github.com/Accenture/sfpowerkit It supports login with username-password combination (probably will need security token as well). A functionality that the standard CLI lacks


Top 50 recent answers are included