great tips to use salesforce inspector reloaded !!!
@jnslzr2 ай бұрын
dancing pandas do sell CRMs after all 🤣
@euuIgor5 ай бұрын
Thank you so much!! This is really helpful. The migrate to flow tool sucks, and it creates a gigantic flow with way too much nested decision elements.
@briankwong72765 ай бұрын
glad you found it useful. Thanks for the feedback. It's been a while since I've did one of these videos so let me know if there's something specific you want to see.
@igorkudryk Жыл бұрын
My life is actually GPT now :D Nice way to put it. Thanks for the video!
@Black_Nemisis Жыл бұрын
How do you set up call recording transcriptions.
@kwarkvikernes Жыл бұрын
bakvet
@JodieMiners Жыл бұрын
Excellent Demo Jen! That Flow demo was such a cool demo showing all the new features. One downside of Notifications are as soon as a user has 20 Notifications that are unread they will get no further notification bell icons... All my users suck at clearing their notifications. I do prefer a Toast for a new record creation.
@forcecopia Жыл бұрын
Thanks Jodie, I wasn't aware of that limitation. I like the toast message approach as well but for demo purposes this worked :)
@rajbhattacharjee532 жыл бұрын
so instead of "migrate" you are showing how to manually recreate each PB as a flow?
@sneakyomni2 жыл бұрын
I think this depends on your definition of migrate. When this was create there was no migration tool for PB to Flow. So if you were going to move out of using PB and to Flow you are create your own flows. It's still a migration. It's just not happening through a tool that creates the flows for you
@Mikeelianne2 жыл бұрын
this is really helpful understanding flow components. Thank you so much!
@PinkFosterMobile2 жыл бұрын
Cute jacket and presentation.
@SuntzuMocro2 жыл бұрын
The only channel for which the bell is turned on.
@SalesforceBreak2 жыл бұрын
Great summary of orchestrator's capabilities. Also awesome points about the gotchas of the UI. The trick about creating a vaiable marked for output and setting the default value to the screen component is pretty neat. I usually use an assignment for that. Cheers.
@briankwong72762 жыл бұрын
Using an assignment would definitely make it more apparent. Of course, it's also uses up an element when you don't HAVE to. I don't think either is necessarily better than the other unless you're hitting up to the 2000 element limit Thanks for the comments & thoughts
@SalesforceBreak2 жыл бұрын
@@briankwong7276 I started building one yesterday and I definitely don’t like the x to save and get out. It is a UI mistake.
@Pseudonym10212 жыл бұрын
Thank you Brian. It's 2022 and flow builder looks very different but your video is the only one I found that made it possible for me to do such flow
@sneakyomni2 жыл бұрын
Glad the old stuff is still helping. I've tried a few times to reboot and make these with the new builder, but by the time I get things built - they change something that requires me to do it over again!
@hrishikeshj2 жыл бұрын
Very nice content - however the video is not clear; can this be fixed?
@sneakyomni2 жыл бұрын
It's a live stream video and not recorded. It was streamed at 720p. not much I can do about it. It looked fine when it was streamed so not sure why the resolution isn't as sharp as it was when it was streamed
@hrishikeshj2 жыл бұрын
@@sneakyomni - ok, not a problem
@forcecopia3 жыл бұрын
Great step by step on converting workflow rules to Flow! I also appreciate the added best practices & things to consider. Where is your hat Wizard?! : )
@michaela.grandel89173 жыл бұрын
Thank you so much. This is exactly what I needed tonight.
@briankwong72763 жыл бұрын
Yay Glad it helped
@addisonhayden12163 жыл бұрын
Keep up the great work!!! Good luck with growing your channel! Did you ever check PromoSM?! It will help you get your videos higher in the KZbin search results.
@EvanNatelson3 жыл бұрын
Is this still possible in Salesforce?
@briankwong72763 жыл бұрын
I know for a fact it works with Classic email templates since I just did one with a formula not too long ago. I haven't had a need to try them with Lightning Email templates. I would expect that would still work
@tnesseth5473 жыл бұрын
this is great. but youre showing the end result of a "how to" people are searching for. is there a place not littered with cheap google ads that one might find shelter and some actual assistance?
@eduardovalentimneto4523 жыл бұрын
You are very special alicia.
@srikiranat4 жыл бұрын
This is very helpful, Thank you! I am having an issue with the decision. What ever I select in the 3 options, it always shows me the first screen. What could be the issue?
@briankwong72764 жыл бұрын
It depends on what your outcomes are. They are evaluated in order. So if you have 3 outcomes and the criteria would be true for both Criteria 1 and Criteria 3 - only Criteria 1 will be evaluated. So it's tough for me to give you a straight answer without looking at what your outcome criteria are. The most common issues I see are either wrong long (equals instead of not equals), empty or incorrect variable references, or you have multiple criteria which would evaluated to true and the first one gets selected
@srikiranat4 жыл бұрын
Brian Kwong ok, got it. Thank you for your response. I figured there was a technical issue on my end.
I had planned on releasing episode 6 many months ago, but life has caused me to prioritize what little time I have between family/work. Doesn't help that there's basically no quiet time to record anymore. I do have some plans. There's been enough changes in Flow and even more coming in Winter '21 that I'll likely wait until Winter '21 is released and go from there. Flow is going to be THE automation tool to use in the future for Salesforce - when you're not needing apex
@n.g.94604 жыл бұрын
Awesome video, thank you!
@jakubd.22334 жыл бұрын
Perfect! Many thanks for the simple tutorial
@elizabethgilbert79734 жыл бұрын
Thanks for these flow highlights, we’ll spent time.
@markjones66924 жыл бұрын
Thanks for the video Brian, I'm trying to get something similar working, I've followed your video to set up the necessary steps ... similar to your example I want to select multiple records, and update a single field in them. In my example, it's records for a custom object called Check-In, where I want to update a date/field called Check-Out Timestamp with the current date/time. So I haven't needed some of the steps set up ... however, my flow is only updated one record no matter how many I select. Would you happen to have any advice? I can easily send over screenshots if that's helpful.
@briankwong72764 жыл бұрын
You're either doing a separate update for each record, or you need to loop through records, set a new value, then update all the records out of the loop. This can be tricky when you want people to select the records. So in my example, I use a record choice set to get a list of the potential records, then do a get records after they selected them. The loop is going through each one. This may be easier now that Flow has stopped requiring you to create your own variables for Gets and Loops
@ophiercohen87254 жыл бұрын
This video got me really excited!!! Question: I tried this for the first time with auto launching when an Account is created. I wanted to use logic for robust Lead field mapping. I only mapped the Id from the Lead to a custom field on the Account. 1. (Get Records) to save all the Lead fields from that custom field. 2. (Assign) the new account fields from the Lead (Get Records) It will not let me Convert my lead. Any Ideas? Some of this flow's variables were set when the interview started. $Record = Account (No ID) Thanks
@briankwong72764 жыл бұрын
Lead convert is a weird duck. I typically don't try to have automation run during the convert process unless I'm overriding the convert process completely with my own custom thing. I don't quite understand what you're trying to do. Converting a lead is just like an edit so if you're doing a before save flow it'll fire when you're converting the lead.
@dhanavellachamy4 жыл бұрын
Is there any way to get the recordID of the newly created record from the lightning component back to the flow? We are not able to auto/prepopulate some of fields (like Country/State as they are picklist through the Lightning component). If we can get the record ID, we were thinking if we can update them in the same flow that called the lightning component
@briankwong72764 жыл бұрын
If you're doing a redirect in lightning as an action - no. The flow essentially ends at the redirect.
@paulcarass4 жыл бұрын
Nice explainer video Brian. Flow has never been so easy for new users to get on board with it :D
@briankwong72764 жыл бұрын
and from the sound of it, Flow will become even easier
@AaronDGoldblatt4 жыл бұрын
Great video! Really looking forward to some of these new features. I think my favorite is the ability to run a flow BEFORE the record is officially created. While testing is required for various situations, I think this will potentially make SF feel quicker to my end users.
@briankwong72764 жыл бұрын
Just make sure you don't go wild and create a bunch of flow triggers on the same object. I agree it should make those simple record updates MUCH faster
@lindathompson24814 жыл бұрын
Your flow is exactly what I need. Any chance you could create and share this in the new FLOW tool?
@briankwong72764 жыл бұрын
yes! it's on my list of videos to make. I'm just very far behind because of Work/Family and flow team keeps doing updates that make my stuff outdated :) Glad you found it helpful
@lindathompson24814 жыл бұрын
Thanks for your reply. I urgently need to deliver something. Any chance you could provide the basic steps in using the new FLOW tool?
@briankwong72764 жыл бұрын
@@lindathompson2481 It's pretty much identical setup. The difference is that instead of "Fast lookup" it's Get Records. And you are saving multiple records vs just the one. You don't need to set a variable to store the collection - that's done for you now. Then you're looping through the collection. Instead of a Fast Update, it's just an update records. Everything is pretty much identical.
@briankwong72764 жыл бұрын
I know it's not much, but here's a screenshot of what the flow looks like now twitter.com/Kwongerific/status/1221868614539673600
@lindathompson24814 жыл бұрын
@@briankwong7276 Thanks very much for your quick reply! Since I never used the old tool I've been unable to translate examples from the old to the new tool. I have another question: 1) I don't need the user to pre-select which records to update. I simply want the screen to dynamically display each record to update based on passing the logged in UserId to the Get records query. (example: Client Lead = $User.Id). Do you know if that's possible?
@tcobbett4 жыл бұрын
Greatly deserved and overdue. Thank you so much SteveMo for your amazing contributions to the Salesforce consulting world, and to me and my clients in particular!
@dhanavellachamy5 жыл бұрын
I am very new to Salesforce and Flows. The flow builder interface in my instance is very different from the one you demo-ed. I dont see Fast Look up, instead can I use the Get Records?
@briankwong72765 жыл бұрын
The interface you see in this video is the Cloud Designer. It was recently replaced with the lightning Flow builder which you see now. The UI is different, but the concepts are the same. There were some Simplifications. "Get records" is basically a combination of the Fast Lookup and the Record Lookup from the cloud designer. The difference is in the options you select. You'll want to store fields in a single variable (a record variable resource) to get the equivalent. The other option requires you to create a variable resource for each field from the record you're getting. That's a big pain in the backside IMO.
@dhanavellachamy5 жыл бұрын
@@briankwong7276 I tried using the Flow builder and now I am getting the error where the lightning component is called as "C:CREATEAXPROJECTRECORDS (LOCAL ACTIONS): AXProject Inputs: InputContactID = {!varContactID} (0035500000T8bE4AAJ) InputAccountID = {!varAccountID} (0015500000Uz4OEAAZ) ________________________________________ Error Occurred: Action failed: c:createAXProjectRecords$controller$invoke [varContactID is not defined] " I have posted a question in the stackexchange, can you please help me with this salesforce.stackexchange.com/questions/290417/quick-action-and-flow-to-create-a-record-in-ligthning
@LetsPlaySalesforce5 жыл бұрын
Good thing he's based in Boston or they'd have to make it GDPR compliant
@XalphYT5 жыл бұрын
More points delivered.
@reeseysmith4865 жыл бұрын
What about record types? I need to let my users create a new custom object record, choose a record type and then be directed to the new record on save to "finish" steps.
@briankwong72765 жыл бұрын
Hey Ruth, You can specify the record type within the Lightning Component like this: ... “entityApiName”: “Opportunity”, “recordTypeId” : “012F0000000rzBdIAI”, “defaultFieldValues”: { ... You still need to know what that ID is. If you want your users to select you have a few choices. One is to create another Lightning Component to let them select the ID. The second choice is simply use a Flow. One way is to create a choice for each record type name then present that as a radio button or picklist in the screen element. You can do a get Records to get records query the RecordTypeIDs based on the name selected. The second, and better, is to create a "Record Choice Set" this combines the Choice and the query so it'll give you the available record types to choose from based on the criteria you set. This way if you create a new record type in the future for that object, your flow will automatically include it. Once you have the ID selected from the Flow you can pass it into your Lightning Component just like it's a field value.
@reeseysmith4865 жыл бұрын
@@briankwong7276 ok, thank you. I have been searching the community for two days for a solution- finally found a post that referenced this blog. Should have just come to you first place. Going to go give this a shot. **not sure she can do this**
@briankwong72765 жыл бұрын
@@reeseysmith486 You can do this. It's one of the reasons I like this solution because there's no apex code. A few tips - read the blog that goes with it. You can copy/paste the sample code from there. Links in the description & in the video. Lightning Components are case sensitive and picky (for example myfield__c will cause an error where Myfield__c would work). Copy/Paste from the API name in object manager whenever possible. They also require MyDomain and Lightning. Don't do everything at once! Don't worry about the record type, start with just opening up a new record (passing no values in) through the flow. Then update the lightning component to accept inputs and pass it into the defaultfields... incrementally add things - you'll be more successful. It's easier when you go "well this worked before I did X so therefore I did something wrong in X" instead of "I built this whole thing and it doesn't work and I don't know why"
@reeseysmith4865 жыл бұрын
@@briankwong7276 I am working on this right now - I struggled with flows before they changed the interface, now I have been doing a lot more with flow. Being in the new interface I am stuck at the create record component- what did you do differently that calls your Lightning Component? I have also run into a snag with the record type...the choice set is returning the type ID vs the name. Still playing with that.
@briankwong72765 жыл бұрын
@@reeseysmith486 It's used as a local action in the flow. If you look at the video kzbin.info/www/bejne/Zp3Tip2nmt2CotE&lc=&t=6m1s you'll see a element with a lightning bolt. That's the action. In the new lightning builder it'll be an action that you can drag onto the canvas, you may have to search for it by name.
@somerslow5 жыл бұрын
I see a comment appearing on 8:20 indicating failed naming convention. Where can I find documentation on this naming conventions??
@briankwong72765 жыл бұрын
Stefaan, That message is something I created. There is no naming convention documentation. I pointed it out in the video because I failed and didn't use my own naming convention that I had previously created & used in other videos. The important thing it to HAVE a naming convention and be consistent. It's not a salesforce this, just a best practice for organizing and documenting your own automation
@somerslow5 жыл бұрын
@@briankwong7276 Hi would you be so kind to share your own naming convention. It can inspire us to setup our own naming convention
@briankwong72765 жыл бұрын
@@somerslow Sure, maybe I thought I had a post on this already, but I guess it was just done for a Dreamforce presentation. So I like to start all my variables with "vr" because I can quickly use the text filtering to get to them. This was more important in the cloud designer than Lightning Flow Builder because the two displayed options differently, but I still use this. I use other prefixes for other types of things. I also use "col" for collection. variable: vr Text template: txt Formula: vrf record variable: vrSo (short for variable sObject) record variable collection: vrSoCol
@MeenuSankar_rahul5 жыл бұрын
Your video is really helpful. Thanks. One of the most excited thing for me about Winter'20 Lightning flow - Lightning flow now support LWC components from Winter'20 release. unofficialsf.com/adding-lightning-web-components-to-flow-screens/
@briankwong72765 жыл бұрын
Since lightning components are no longer the "in thing" I was glad to see we can also use lightning web components as well. I wish I had one built to use in the video for a demonstration.
@zacotero92435 жыл бұрын
I haven't messed around with Flow in a good long while, so thanks for walking through all these new features Brian! Very Helpful!
@briankwong72765 жыл бұрын
Thanks Zac! Anything you want to see about Flow? I'm still writing up future episodes for Wizard Apprentice Flow
@niravtejani3375 жыл бұрын
Thank you so much for the video. I want to call apex class from new Lightning Flow builder. Could you please help me to achieve this?
@briankwong72765 жыл бұрын
Thanks for the feedback. You need an invocable apex method. You can find more information here: developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_annotation_InvocableMethod.htm If you need more I would recommend asking at success.salesforce.com and join the automation group.
@reeseysmith4865 жыл бұрын
I commented "no no" as a joke but then deleted it.
@briankwong72765 жыл бұрын
so you do want us to cancel the WizardCast? :)
@reeseysmith4865 жыл бұрын
@@briankwong7276 ha ha NO do not cancel it.
@adelselim51845 жыл бұрын
Excellent content. I have a question is it possible to loop through two collections and compare values? I want to find the non matching
@briankwong72765 жыл бұрын
Thanks for the comment Adel. Yes, you can technically loop through 2 collections. So we could have Collection A be a group of numbers 1,2,3,4 and Collection B have 3,4,5,6. You loop collection A and within that loop Collection B and do a decision where if This A = This B then blah blah. Things where this doesn't work is if you have a collection of records and you want to get the related or child records. It will work but you run a high risk of hitting limits pretty quickly. It's never a good plan to do any Get Records, Record Updates, or Record Creates within a loop. I have two older videos on loop that use the Cloud Designer. So the flows look different but the concept is the same: kzbin.info/www/bejne/pYK4hqyIjKhkbck and kzbin.info/www/bejne/aIG8eXyPa9-eZ5o
@adelselim51845 жыл бұрын
@@briankwong7276 thanks Brian. The 2nd part of your comment is what I am facing. Collection A is a record collection variable that has 3 records. I want to compare the id of each record in this collection to another record collection variable. I can't find a way to say if Id is not found in the collection ,.do blah blah blah. Hope I am explaining it correctly. Is there any other approach to achieve this other than Apex?
@briankwong72765 жыл бұрын
@@adelselim5184 OK Let's call the collections A and B. So you would have a loop element looping Collection A. Then a Loop for Collection B. Then a Decision Element. So when you create a loop you have to specify the variable to represent 1 item within that Loop. Your decision would be after the 2nd loop and basically look at ThisA value equals ThisB value. If that outcome is matched it goes to another element to do what your "Something" is Your default outcome would point back to Loop B (to check the next B value) and the End of Loop B points to Loop A (to check the next A record). So your flow would look Loop (A) -> Loop (B) -> Decision Outcome 1 (A and B Matches) -> Other elements that you want to do something -> Back to Loop B Default Outcome (A and B do not match) -> Back to Loop B Loop B (After all values are looped) -> Loop A
@adelselim51845 жыл бұрын
@@briankwong7276 with some manipulation it worked. Thanks
@briankwong72765 жыл бұрын
What features are you looking forward to?
@LetsPlaySalesforce5 жыл бұрын
Great to see this content! Just ordered myself a flowniac shirt too.
@briankwong72765 жыл бұрын
Thanks! I'm in the process of making the second episode focusing on the screen element. I'm always happy to take feedback. Also thank you for ordering a shirt! Goes to help offset the costs of stuff and fun my kids' college fund:)
@SK-qv5cm5 жыл бұрын
Is there any way to add a custom Lightning component now? I can't seem to find that option in this flow builder version.
@briankwong72765 жыл бұрын
Yes. I believe it's under core actions. You won't see them listed off the left menu like the cloud designer. It's buried in the Action menus
@ucfjeans29115 жыл бұрын
Brian Sir, Its a Very Nice Tutorial...Please Upload Some More,,,With More Magical methods..
@briankwong72765 жыл бұрын
I'm in the process of re-making all the older version with the new flow builder then I'll have some even newer stuff coming out. Thanks for the feedback!
@hemanthtanguturi95635 жыл бұрын
You are my life saver....
@briankwong72765 жыл бұрын
Glad I could help! There's a blog post in the description with other details including a link to something Doug Ayers put together that uses only a lightning component. His solution does require some coding to work, but theoretically would make it more reusable.
@Staffadora5 жыл бұрын
I was wondering how to get the values from a component that is in the flow builder? does anyone know?
@briankwong72765 жыл бұрын
depends on what you mean by this. You can pass values INTO the flow a number of ways. The variable needs to be marked as "input" and then you can see it in Process Builder (if you're going that route) or a quick question (if going that route). Getting values out Flow, you set the variable to "output." Then it's a matter of what you're outputing to. Apex? Something else?
@gabrielmcginn25085 жыл бұрын
RIP Copy/Paste/Undo :_(
@briankwong72765 жыл бұрын
Well for the moment. Shannon Hale, the new PM of Flow Builder, has stated publicly those features will be coming. It just wasn't ready for the release right now. Personally, I find I only then need them when I'm building a brand new flow. So I may go to Process Automation Settings, remove the check box so I can use the cloud designer. Copy/Paste what I need then turn off the cloud designer and go back to the Lightning Flow builder
@gabrielmcginn25085 жыл бұрын
Yea, I figured it would get added, I am just missing it right now :)
@gabrielmcginn25085 жыл бұрын
In the interim :D unofficialsf.com/converting-a-flow-builder-flow-version-back-to-cloud-flow-designer/
@neilmoses29576 жыл бұрын
I'm interested in the Screen Component File Upload. Do you have a working example for this?
@briankwong72766 жыл бұрын
I don't have anything available, but that sounds like a Great video option. What's your use case for using the file upload?