Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with package
Search options not deleted
user 77444
A package is a container used to distribute something as small as an individual component or as large as a set of related apps.
3
votes
0
answers
40
views
Managed package -- error in field names in decisions due to namespace prefix
I run into a problem after deploying a package with a namespace. Found an error in a decision within a record-triggered flow. … I found it happens in every decision component around every flow in the package.
Yes I can fix the flow by changing the field in the resource to:
{! …
- 121
0
votes
1
answer
70
views
Insufficient privileges when adding fields in package (changeset)
I am getting an "insufficient privileges" error when adding fields (yes, just fields) to a package I'm building, despite the fact I'm system administrator using a DE (I am creating a brand new application …
- 121
0
votes
Insufficient privileges when adding fields in package (changeset)
Well it was the "change set helper" plugin. Sorry.
- 121
1
vote
1
answer
136
views
Problems deploying (brandingset) via VS Code
I have this package.xml:
<types>
<members>LEXTHEMINGTR2C2</members>
<name>BrandingSet</name>
</types>
...
<types>
<members>R2C2</members>
<name>Lightnin …
- 121
1
vote
Problems deploying (brandingset) via VS Code
I made it!
As it turns out (in a trial-and-error exercise), the prefix "LEXTHEMING" is useless. I removed any reference to the prefix.
In the package.xml I just let the branding set name as it was:
<t …
- 121
0
votes
0
answers
26
views
Install unmanaged package avoiding B2C capabilities
I have built an unmanaged package and I need to install it onto another Salesforce org. … We made a terrible mistake by enabling person accounts, and now I can't install the package because the destination org needs to enable person accounts, but that's exactly what I DON'T want. …
- 121