You will be spending a lot of time by working on the complex logic like this. Better fit an apex class with this and solve with the code than breaking your head. Low code means saving time. And if low code is saving your time, do not go with it.
A doubt!!! I have around 3523 assignment rules for 4 territories inside a model, that is manually an exhaustive task can we do it through code? Any ideas on this?
I believe SF came out with Roll back feature in flow ...so now instead of invocable action , we can use Roll back in fault path to uncommit the changes ....is this correct ?
How did you do the Rest of PA. I am in a similar situation where I want certain zip codes and everything else but can't figure out how to exclude those zipcodes in everything else.
My issue with this class is I thought it's supposed to be for beginners?? Your first examples jumped from kindergarten to 4th grade. It would have been nice to start with super simple formulas like (variable) -25 and show how they formulas are built.
Regarding the demo, after the Weekly Snapshot is created, the flow runs the second decision to check for the Monthly Snapshot. The second decision is connected back to the Weekly decision. Won't there be an unending loop? because I was thinking once the Monthly snapshot gets created, it enters the Monthly decision again and connects back to the first. Am I reading this wrong?
Paul - when you are in the loop processing the data is is ok to do more DML Get Record calls? This pattern looks like it would solve my issue but i need to grab some information from other child records within the loop. Everyone says "do not use the DML options in a loop" but I need that other data.. Thoughts?
Took over an org that had be unmanaged for a bit and was built with all the admin 'not-to-do' rules. Upon rebuilding our org, I discovered that ETM was feature available to us. Attempting to find all the information I could to understand how to set it up, this video was the most helpful to understanding how ETM works. It was also great seeing it used with flow because the minute I learned it existed, my first thought was "how/can this work with flow?". Great information.
Can you use this collection functionality to collect cc'd email addresses off of inbound emails related to a case, to then send out an auto reply flow email alert?
I have a community with a screen flow that looks up a user account. The lookup loads ok & debugs fine while logged in as a regular SF user. Issue I have is I can't do it as a guest user. I can search but no results. Seems like I'm missing a permission somewhere. I have a custom object set for lookup to user. the guest user has access to that. Anything else I can check?
Good explanation but the FlowScreenComponentsBasePack in an error, I tried to install several versions Error: 1. Apex compile failure Apex class AccountsPayableOrderService: line 104, column 55: Variable does not exist: CASE_WITHDRAWAL_CAUSE_LACK_KNOW_HOW 2. Apex compile failure Apex class CloneCaseController: line 46, column 64: Method does not exist or incorrect signature: void getCompletedCaseMilestonesPerCase(Id) from the type CaseMilestoneSelector 3. Apex compile failure Apex class UpdateRepairInfoController: line 198, column 56: Variable does not exist: CASE_WITHDRAWAL_CAUSE_LACK_KNOW_HOW Thanks
Hi. In 2nd flow that you created and how did you create collection variable? I tried by creating collection variable of record data type and object assignment group member. And when I chose it and tried assigning to current loop from get group it asks for field. Am stuck with this step . Could you pls elaborate
At around time stamp 47:01 Terry mentions where he has his posted his own variables naming conventions, but he spoke kind of fast and it's difficult to hear. Can location of where to find that list of his preferred naming conventions be confirmed?
I don't think my current org is crazily complex, but we already have many automations on various objects. Having one flow per object, even just for when records of that object is updated is restrictive because it means if one sub-flow under the master flow fails, all other sub-flows will fail since they are in one transaction. I think restrictive entry criteria, Flow Order of Executive, Flow Explorer and Flow Orchestrator took care of the question One Flow or not to One Flow Per Object
Has anyone had issues with the record details showing? I configured the table and saw test data but when I tried it none of the fields were rendering even though there were several rows
Hi! Thanks for the video. Maybe somebody encountered an error: Uncaught Error? Invalid attempt to set a new value for property isDisableSuppressBottomBar of [object:vm ers_datatableCPE (612)] that does not has a setter decorated with @api
Thanks for the video. This datatable component is great, however we are experiencing an issue with our use case. When we use the component and ask it to display a record collection that only has one record the table does not display. Anything with more than one record works perfectly. Any idea how we may be able to fix this issue?
