New answers tagged error
0
You can put the two together you in an if statement. I assume you have some logic that needs to be true and provided that is not true then the RaiseError is what you'd need to run after.
You can setup the if statement like below:
set @var1
set @var2
set @var3
set @colvar1 = attributeValue("column_name1")
set @colvar2 = attributeValue("column_name2")
if @...
0
Since my use case is a scheduled flow, the following worked. The idea is to make it asynchronous by adding a Pause element.
https://success.salesforce.com/ideaView?id=0873A000000COJ1QAO
2
Yes. What you should do is the same as you'd do in a trigger. Get the list of elements, loop over each item, then update the collection. Here's what that looks like:
This is, of course, a Visual Flow, but the same rules would apply for autolaunched flows as well. Query, create or update records in memory, then commit all changes.
4
Because of the locker service, JSPdf is not supported in LWC. Check my answer to generate pdf in LWC using standard browser API.
1
Rather than writing a series of OR clauses, use an IN clause to match many potential Ids.
Select ID, ParentId, RecordTypeId, OwnerId
FROM Account
WHERE Active_Client__c = TRUE
AND ParentId = null
AND RecordTypeId = '0111xxxxxxxxxxxxx'
AND AccountId IN ('0011111xxxxxxxxxx', '0011111xxxxxxxxxx', '0011111xxxxxxxxxx', ...)
You shouldn't ...
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 ...
0
You just have a couple of issues with the format (it needs to be valid JSON)
Here's the format corrected:
({ // Load expenses from Salesforce
doInit: function(component, event, helper) {
// Create the action
var action = component.get("c.getExpenses");
// Add callback behavior for when response is received
action....
0
I got the answer here: https://success.salesforce.com/_ui/core/chatter/groups/GroupProfilePage?g=0F93A000000HTp1SAG&fId=0D53A00004Y40q1SAB
There is a known bug for this. If you have an object (abc__c) in a base package (PackageA) and then you try to add a workflow for that object in a dependent package (PackageB) and PackageB is defined to depend on ...
1
For your 2GP packages, you need to use the name/versionNumber format for your dependencies:
"dependencies": [
{
"package": "ParentPackage",
"versionNumber": "0.1.0.LATEST"
}
]
It took me a little while to figure this out myself.
Also, make sure you do not have an object-meta.xml file in the root of each object folder for the child ...
Top 50 recent answers are included
