The best practice while working on flow avoid hard coded ids , and manner naming convention and Optimize the flow
@TechJourneyWithAnkitАй бұрын
You are missing a few important things my friend
@user-jb6cn9ej5mАй бұрын
@@TechJourneyWithAnkit It seems there may be some important details that we might have overlooked. Could you kindly clarify or share those points with me? I would greatly appreciate it. Thank you!
@BeyondMayaShorts-si3isАй бұрын
Sir what is the most important difference between record trigger flow and triggers? And which should be used and in which scenario.
@TechJourneyWithAnkit29 күн бұрын
Bulk processing of record or complex business logic go for trigger else go for flow
@kavithaalluri77932 ай бұрын
Thank you for uploading Sir, I requested for flow interview questions earlier.
@TechJourneyWithAnkit2 ай бұрын
I hope you found this helpful
@kavithaalluri77932 ай бұрын
@@TechJourneyWithAnkit yes Sir, but volume is very low for this video. All other videos are good. please take care of the volume next time. Also I request you upload interview questions related to deployment process, CICD and GitHub.
@srinivasvenkata85058 күн бұрын
Can we execute multiple paths (not async and sync and errorfault) in single flow transaction without using desicion element
@TechJourneyWithAnkit7 күн бұрын
Yes in record triggered flow
@AnilKumar_781Ай бұрын
Hi Ankit- Thanks for sharing this Video. Could you let me know what is this major difference between "Fast fields updates" and "Action and related records " in flows. Is this comes under types of flows we have? How many flows can be written for an object as per best practice? Thanks for your time.
@TechJourneyWithAnkitАй бұрын
It comes under record triggered flow. Fast field update is used if you have to update the field of triggering record else go for Action and related record.
@awesomekj58122 ай бұрын
Thank you for sharing ...hard to find videos online for this stuff..
@TechJourneyWithAnkit2 ай бұрын
Glad to help
@ranjitabehera93332 ай бұрын
Thank you for this informative video 😊
@TechJourneyWithAnkit2 ай бұрын
Glad it was helpful!
@himanshubansal68092 ай бұрын
are u going to upload more video on flow or one video is enough?
@TechJourneyWithAnkit2 ай бұрын
One video is enough. If you have any questions let me know
@rockyomkar412 ай бұрын
Post some videos of flows for easy learning.....!
@TechJourneyWithAnkit2 ай бұрын
Sure will plan for it
@Rohitkumar-vg5xi2 ай бұрын
Can we create a map collection in flow ? I guess no
@TechJourneyWithAnkit2 ай бұрын
Nope
@Acoustic_ash2 ай бұрын
Please make interview video related to field service lightning
@TechJourneyWithAnkit2 ай бұрын
No experience on that
@awesomekj58122 ай бұрын
Another thing I believe true for Before save is that --> you cannot access related records whereas in AFTER SAVE , you can access related records. Also BEFORE save does not have INSERT element I believe ....whereas AFTER has it 1. I believe you cannot do Undelete via flow 2. We can subscribe to it via creating platform triggered flow which listens to Platform Event object record creation in system 3. You can publish platform event by creating PE object record 4. Best Practices --> naming convention , Always have fault path with DMLs , No Hardcode ID , Save Record that triggered the flow in variable , Bulkify Flow .