วีดีโอ

Hey Conni, thanks so much for your feedback and I'm so happy to hear you found this video helpful. Great question, by the way! You can achieve this by having two Get Elements at the beginning of your flow, one for Account and one for Contacts. They can both reference the same 'RecordId' variable so no need to duplicate this. The reason behind it is that you will either be launching the flow from the Account OR the Contact - so the flow will check for the first Get Element, if it finds a record it will populate the variable with the ID (in which case the next element will fail - that's ok). If the flow doesn't find a record in the first Get Element, it will find one in the second. This means your variable will always have either the Account OR the Contact Id. Hope that makes sense. Bit difficult to explain on a comment but let me know if this needs a better explanation and perhaps I can do a quick video about it.

@@paduarte my recordId is a record variable to store the related Contact ... will the get elements still work?

@@ConniStock If you're only using the RecordId variable at the start of the flow in a Get Elements for Contacts, then yes, you can just have another Get Elements for get Account and reuse the variable - because it will always only find either a Contact OR Account (never both).

Thanks for the feedback and the sub! 💪🏻

Hey 👋🏻 Can you walk us through your use case in more detail? Are you trying to use a Action Button within a Screen Flow that just creates a new record? What would this new record be related to? You might be able to skip the 'get Opportunity' step in the video but it depends on your use case

Hey 👋🏻 Thanks for the feedback and great shout. I went back to actually test both functionalities to ensure the documentation is inline with flow expectation - and you're right, skipping doesn't create or modify any records. Thanks for highlighting this. I'll add to link to the documentation so others can see it directly: help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_builder_check_for_duplicate_records_with_the_updated_create_records_element.htm&release=250&type=5

Hey Chelsay 👋🏻 Thanks for checking out the video and for your feedback! You're right, seeing examples of Documentation is difficult - mainly because people/companies do it differently and they don't like to share. I'm going to try to put a video together that goes over some examples, but until then here is what I would recommend for you to do, as a new admin: 1) Use a Word Document (or similar) instead of Excel 2) Pretend you're writing an essay back in school. Create a heading for each Object and/or Company Area and under the heading, explain everything you can, such as: What it will be used for, the challenges, the proposed solutions, the desired outcome, who will use it, etc. 3) after you do this for all the objects or company areas, you can go back and add diagrams (if you'll be using them). Diagrams is a great way to visualise business processes. 4) Before you start building or making changes, ensure this document is signed off by a decision maker in the company. The purpose of the document is so that if you, or anyone else, ever have a question about the system, say for example ' What do we use Accounts for?' - then you can go to this document and find your answer. If your document does that - then you know you have a well documented project. Seperate to this document, when you build out objects and automation, you can create other documents that are dedicated to these processes. You'll find some people refer to the first document as a 'High Level Solution Design Document' and the second as a ' XProcess Design Document'

@@paduarte Wow! Thank you SO MUCH for the detailed explanation and some names of things I can Google for later on. That was all VERY helpful!!!

Awesome. Looking forward to hearing an update 👍🏻 This is the Seller Home. It's the new default home page if you don't have a customer one. You can find out more here: help.salesforce.com/s/articleView?id=release-notes.rn_sales_features_core_seller_home.htm&release=248&type=5

Hey 👋🏻 Do you happen to know which release your Dev Org is on, by any chance? If there's nothing on it that is of value to you and you just wanted to try out the Intelligence View, I recommend spinning up a new dev org - that should have the options available

​@@paduarte Hey I checked the version of my Org where I am unable to find is 'Version Summer '24 Patch 13.5' So Ideally it should be there as this is the release where Lead Intelligence view is introduced. On the another side I created new playground of trailhead and i am able to see this new feature. Please suggest what I can check to see this feature in my org?

Hey @@nehaagrawal3359 - yeah the way to check would be to add your instance to trust.salesforce.com/ so you can double check your version. Glad you manage to get access to it in the end though. Do triple check to ensure you have the updated version

Thanks for the explanation. The Flow Interview ID makes sense here, which is easier to remember :)

Hey 👋🏻 You have some options, yes. For example, suppose you Upgrade the Record Detail Component but want to revert it back. In that case, you can delete the Dynamic Record Detail Component from your Page, and add a new Record Detail Component (this won't be Dynamic until you Upgrade again). Alternatively, since it is a Lightning Record Page, you can create a New Page, and replace the old one.

@@paduarte Hi my doubt is when I clicked on upgrade now after that Edit option for field is gone...I am not able to edit the field Previously before upgrading it was available

@@pratikjire3717 Hmm what do you mean when you say 'edit option'? Are you referring to when you select a field after upgrading to Dynamic Forms (under the Field Section on the right hand side)?

@@paduarte like before upgrading page on sections we will have fields right? So That was editable but after when i upgraded to dynamic form I am not able to edit the fields on the sections

I haven't been able to find a way to do this. I guess Salesforce is really pushing the Automation App - very annoying indeed though

@@paduarte You can say that again :-D

Oi Marcos. Haha, muito obrigado 💪🏻

Hey 👋🏻 Thanks for taking the time to give your feedback!

Yeah so true! I'm really hyped for this. Can't wait to get hands-on!

Zoho CRM UI best more SF

Years in the making! 😊

Hey Michael, The article isn't very clear on this but I suspect (my best guess) that this will either 1) be rolled out for everyone, so it becomes the new default UI or 2) you switch between current Lighting and this enhanced version, much like you switch from Classic to Lighting at the moment.

Gabriel, thanks man! I appreciate the feedback 💪🏻

Nothing that I could find yet. I'll try to post an update when there's something solid on this

Thanks Eline! 💪🏻 No, we will still have the Console View, but I'm not sure what it will look like at the moment. I'd assume the record pages will look the same (for uniformity) but the tabs would be different, due to the nature of the Console. Lots of mixed reviews on this new UI at the moment. Looking to get hands-on soon and be able to share my opinions in more detail

Really? 😲 I'm really not very familiar with them, so I didn't know! And here I am feeling excited about a FRESH new look!

I do, I'm working on a video to share them. Hoping to be able to release it soon 👍🏻

Full transparency video. Thanks so much for your feedback! 🫶

Thanks for the feedback! Still trying to find what works best so much appreciated 😅

Glad you found it helpful! Thank you for your feedback 🙌🏻

A great question, for sure. Some of these can change over time, but at the moment I would say 1) Classic experience compatibility 2) record type specific 3) mobile accessibility 4) experience cloud. We have already seen lots of improvements on some of these, but not enough to completely replace it IMO.

Knew the rec types and mobile (assuming you’re referring to the compact layout?) but wasn’t aware of Exp. I wish that Salesforce would clarify more with some documentation or something. At least I haven’t found any.

This is SUPER helpful! Really appreciate the info. 💪🏻

It essentially laucnhes a flow, so it works within the limitations of that.

Hmm hard to say without more information. Can you walk us through what you've done so far? 🤔

You are probably logged in as System Admin

Ah really? That's great info! Thx for sharing 👍🏻

So, you put get record and create record elements in the same flow, correct?

Oh really? That's interesting. I need to try again and see if I can get it all under one flow

@@paduarte ​In your case, you would still need two separate autolaunch flows (as you've done). That's because the user must make a decision and select one of (possibly) many opportunities to create a quote. A single autolaunched flow cannot pause to accept user input (like a screen flow). Instead, if you just wanted a table of related opportunities and a table of related quotes, then this could be done with just one autolaunch flow (since it wouldn't require additional user input).

Same thing happened to you? I wondered if it was a bug on the sandbox... On a different env I managed to create a list view for 'Screen Flow' types and it did display the results correctly.

It won't show any flows with an API version below 49. If you just save one of your flows without making any changes that should update the API version and you will see the flow on the app

That's really helpful, thanks @@tjwillis47

Hey 👋🏻 Thanks for taking the time to give your feedback!

Glad you liked it! 👋🏻

Great question. Short answer, yes! Because the Action Button launches a separate flow, you can do a lot of different things. Using the example in the video, I created Quote records. The full capabilities on this functionality, however, will be discovered after full release and official documentation becomes available.

Please do! Let me know how you find it 👍🏻

Thanks mate! Much appreciate the feedback 💥

Thank you! Have you tried this yet?