New answers tagged

0

The below code work for me, hope it will be useful for you: <style> @font-face{ font-family: 'samplefont'; src: url("{!URLFOR($Resource.staticResourceName, '/Path/filename.eot')}"); /* IE9*/ src: url("{!URLFOR($Resource.staticResourceName, '/Path/filename.eot?#iefix')}") format('embedded-opentype'), /* IE6-IE8 */ url("{!URLFOR($Resource....


0

The key issue is you have to update using an Account ID so you will need to first select the records using a Get Records to select the record you what to update, after that you need to Assign the values for the records, then Update the Records using the Account ID (see the image below.


0

Try writing TRUE in the validation rule field, that seems to work. Otherwise the validations do not seem to work very well (at all). The main problem seems to be in accessing the value of the validate field. If you just save it as is and validate afterwards the formulas and validations work like a charm. Such a stupid behaviour is to be expected from ...


1

Obviously your deployment command doesn't take your "--apiversion 47.0" for real. Try increasing your API version in the project file. Or try clearing the .sfdx folder in order to delete any cached stuff, that way it might recognize your requested change in the API version.


2

In order to use conditional visibility with custom LWC components, there are two things that need to happen. Dispatch the FlowAttributeChangeEvent when you want to notify the flow runtime that a change has been made. Use automatically assigned variables in the conditions that need to be notified of the change. As per Flow Conditional Visibility ...


0

The fields which you are updating using flow, may not have edit access for the profile who is using the flow. Give them edit access for the fields at profile level.


0

Salesforce has indicated this is a known issue with no resolution date. https://success.salesforce.com/issues_view?id=a1p3A000001RXPC The workaround for my situation was to use apex


1

Here is the same question and a useful proposed solution from the thread: public with sharing class MySchedulable implements Schedulable { public void execute(SchedulableContext sc) { // Call FLOW to do actual work (no input args) new Flow.Interview.MyFlow(new Map<String,Object>()).start(); // Call FLOW w/ input args - keys are case ...


0

You can achieve it by using a proxy formula variable. This is my test flow: In Get Account element I retrieve the record from the Lightning Page with only one additional field - TestNumField__c which I use to control the visibility of one of Test Screen's components: Here's the defined formula variable: Which I use for setting component's visibility: ...


3

The versioned FlowDefinition object is no longer recommended as of API 44.0, in favor of the unversioned Flow, which is the point at which behavior around Flow versions changed in the Metadata API. Using API version 43.0 or prior to retrieve FlowDefinition should return the original versioned files.


2

If anyone needs this in the future, here's the code: Trigger Trigger OppContactRoleTrigger on OpportunityContactRole (after insert, after update){ AddPrimaryContactToOpportunity.runFlow(); } Class public class AddPrimaryContactToOpportunity { public static void runFlow() { for(OpportunityContactRole ocr : (List<OpportunityContactRole>) ...


0

Because you are using flow, it will respect user permissions. If you were to invoke a visual flow instead and use invokable APEX you could get around this and run in system mode using the without sharing keyword on the class. But what I think is the best approach in this use case would be to use a visual flow and use a session based permission set that gets ...


1

So the issue I see here is that calling a flow is not a bulkified process, but to get you a little further, here is you code reworked: public class AddPrimaryContactToOpportunity { public static void runFlow() { //I admit, this is not bulkified for(OpportunityContactRole ocr : Trigger.new) { Flow.Interview flow = ...


0

Conditional Visibility You could have a radio button group to control the visibility of the other input components (by setting up conditional visibility on them). The options for this radio group would be: Create New Contact Select Existing Contact You could select one option by default to minimise the number of clicks for users. Making Name Required ...


1

The "Lightning StyleSheets" attribute only adds the look of Lightning, but does not actually contain the full runtime. You need to expose the flow in a Lightning App or Lightning Component. Use lightning:flow to expose a flow in a compatible experience.


1

based on doc you should try ISBLANK AND(NOT(ISBLANK([Lead].Source_Opportunity__c)), (ISBLANK(TEXT([Lead].Source_Opportunity__r.Source_details__c)) && NOT(ISBLANK(TEXT([Lead].LeadSource))) && ISPICKVAL([Lead].LeadSource , 'Trig') && NOT(ISBLANK(TEXT([Lead].Source_Opportunity__r.Business_Line__c))) && ISPICKVAL([Lead]....


1

Calling Apex from a screen flow is easy to achieve. You simply have to make sure you can call the code via an @InvocableMethod. The approach I take is to have the invocable method in a separate class (what I call a "facade") that then invokes the required logic on my underlying class. This has a couple of benefits: You can adapt the input parameters to be ...


0

Adding the masterLabel and description attributes, and reducing the target list to a single target (the flow), and removing unnecessary attributes form the properties seem to have solved the issue for me. The only attributes that remained on the properties were name, type and role.


1

https://help.salesforce.com/articleView?id=flow_ref_elements_data_get.htm&type=5 Scroll down on the get record screen and select "Manually assign variables (advanced)". There should be an option at the bottom to specify setting the variable to null when no records are returned. Now, you can add a decision to check if this variable is null.


Top 50 recent answers are included