3
Make sure your flow variable is available for both output and input.
This is likely to fix your issue.
3
You can get the object name from the Id like this
String objectName = theId.getSObjectType().getDescribe().getName();
"theId" refers to an "Id" type variable (not a string). You can cast it from a string like this, Id.valueOf('1234').
Also, you will need to use dynamic SOQL for this. e.g. Database.query('SELECT Name FROM ' + objectName + ...
3
You want to check if it contains non-numbers, so that's what you need to do. The rule should look like:
REGEX({!phone_private}, "[^0-9 ]+")
The ^ operator at the beginning of a character class inverts the character matching, so only 0 through 9, and space, would be allowed.
2
The validate input is actually the opposite of a typical validation rule. In this screen, your formula is about denoting whether the input is valid (true) or not (false).
NOTE
The formula expression must return a Boolean value (true or false).
If the formula expression evaluates to true, the input is valid.
If the formula expression evaluates to false, ...
2
Yes, picklist fields take text input - you can also do this in Apex code.
Multi-picklist fields also store their values as text, semi-colon seperated.
It's only when you retrieve the value in a calculation that you have to apply a TEXT() or a ISPICKVAL() or INCLUDES() calculation.
In code, assigning values to these types looks like this:
Picklist_Field__c = '...
2
Days between two dates (assuming both fields are of type Date)
{!EndDate} - {!StartDate}
The link you provided in the OP was for getting the months between dates which is a harder problem than days between dates
2
I was not aware of the inability to remove flows (1GP beta), so thanks for sharing. However, I believe you are misunderstanding what this means. I believe this is simply saying that flows from 1GP or 2GP managed packages are not subscriber deleteable, rather than set in stone within the package itself when using betas.
In terms of other beta "gotchas&...
2
Unlike Workflow time-dependent actions where the query Object equals Opportunity would work, for some inexplicable reason, when using Flow Scheduled Paths ..
Even though they are associated with a record-triggered flow and the flow's object must be identified
The value of the Object field is not populated in the underlying object WorkflowTimeQueue (...
1
Flows are bulkified, which is why the apex method accepts a list of records. You would only pass in 1 record in the flow, but the apex method accepts a list.
To get around this, your apex method can accept a List<List<sObject>> so that you can pass a record collection variable from your flow into the apex method.
1
welcome!
Formula limits stack, unfortunately. This means that when evaluating the total character limit of a formula, Salesforce will include the logic from the formula at hand, together with any and all formula fields that it depends on. Their total character limit combined needs to be less than the 5,000ish limit.
This basically means you need to use ...
1
For Before Save flows, you need to rely on the Order of Execution to do record validation. This means focusing on steps 3-5:
Executes record-triggered flows that are configured to run before the record is saved.
Executes all before triggers.
Runs most system validation steps again, such as verifying that all required fields have a non-null value, and runs ...
1
Sometimes putting the Get Records inside a loop is unavoidable, as it appears to be in this case. What is the volume you're dealing with? In this case, you'd want to make sure you don't do more than 100 SOQL queries per transaction.
1
If you use HappySoup.io (free and community-led open source project) to see where a field is used, the results will tell you which flows are real flows vs which ones are process builders. This would've saved you a lot of time!
1
In addition to the accepted answer, you can modify your package.xml accordingly. E.g.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
<!-- other types removed for brevity -->
<types>
<members>*</members>
...
Only top voted, non community-wiki answers of a minimum length are eligible
