Record Trigger Flow | Schedule Trigger Flow | Day 6

[@chin2mittal]

Hello, I guess the issue you faced is because by mistake on the last step while updating the Contacts, you selected 'Create Record' action over the collection of Contact which already has non-null IDs.

[@wiama.3467]

Quite confusing this time. And the error at the end was because Amit is trying to create new records...which need all required values assigned. He took the wrong DML-Element at the end. Update Records would be the right one.

[@ragulhm]

From October 9th we are going to have sub flow for record flow. Kindly cover that part as well from preview sandbox. Single flow will not help replace 2000 lines of our company trigger.

[@apexhours]

We will try in future sessions

[@ayushmanshahu9765]

Scenerio works . take update record account id equals null. instead of create record.

[@vanaramprajapati3890]

In this context, you can create a new variable resource and define its data type as a record. Make sure to select the "Allow Multiple Values" checkbox. After creating this variable, proceed to assign "add records" within the assignment block. Within the final loop, you can then update a record. To do this, utilize the previously defined variable of record type to modify the necessary record.

[@derrickchavez8494]

Here is a helpful tip on deciding whether to use the Assignment Action vs. Update element for Scenario 2 at the 20-minute mark of the video. There is very little difference. You can use either the Update element or the Assignment element. The key is that triggers and validations are NOT recursively kicked off in before-save Flows as they are in after-save Flows. This means the performance is almost the same whether you use the Update or the Assignment element.

[@elhadjimoryndaw5773]

THANK YOU

[@apexhours]

Glad you like it

[@massimotarquini1168]

why did you opt for a get record in the scheduled flow rather than the initial contact object chosen in the start element? the first approach you had was more scalable as 250k records can enter the flow

[@mohamedel850]

Can you elaborate more on this please.

[@somsamanta3498]

These are excellent videos with great use cases. Do you have a video series for process builder by any chance?

[@apexhours]

Flow is future

[@shubhamband432]

We should avoid criteria which we added at first step , it should be "no criteria just execute " So we will able to run this flow on collection of records not on each and ever record

[@vaibhavpatil478]

Error you received in last is because you have selected create record element instead of update record

[@tugba5943]

I agree with you .

[@AS-lb8rk]

The scenario 2 - A flow which will run on Contact Records which were created in last week and do not have any related account, where was the part where you took care of contacts which were created in "last week" I didn't see that in the flow.

[@hitashihusband9159]

He took the wrong DML-Element at the end. Update Records would be the right one.

[@muhammadusmanbabar8660]

Amazing seriously

[@apexhours]

Keep watching all sessions.

[@tmukhia]

Hi Amit , I have a scenario where I will be creating a checkbox field (Copy Comments to the Related Cases) and post it in "New Case Comments" action. Now I want, if "Copy Comments to Related Cases" is checked then copy that comment to all the Related Case Comments. Can you please show how it can be achieved? Thank you, Tarun

[@sandireddyroja6991]

Hi I am getting this error while creating task,but currently i am using system admin profile only ,Please help me out here

[@amitbagade3277]

Sir, if i want to create task 1 day after record is created so should i go for Record trigger flow or screen flow? and also it to assign to perticular user in org not owner??

[@balajibasanolla]

19:45 it is not showing the create record because u chose the before insert I think the reason for that is not showing.

[@sharmilajennas3469]

Good Job but a little confusing this time.

[@apexhours]

Looking forward for feedback and we are open to change it. Can you please suggest ?

[@massimotarquini1168]

@@apexhoursI agree with Sharmila; he was very thrown off about the create record element not being available; yet he had a before update operation and the create record element is not available for before events...

[@veeranjineyulukuruva4028]

I have scenario there date field and owner field , when ever owner got changed and date field is today date so i need schedule email alert after 365 days ,so customer need to get after one year . I tried but is changed not possible in schedule folw

[@sevdadalklc8410]

Flow is worked, but there is an error in this flow. Dummy account created but it doesn t have any related contact...Please can you share a video for this scenario again..(Also I think you did wrong with createdrecord in the last part, I did updaterecord but there is still something missing in this flow.It doesn t give relationship between Account and contact)

[@sunalgautam6888]

Its happening because we need to take the ''Current Item from Loop contact..' variable in the Update Records element, try it , it will work.

[@igorferreira1486]

@@sunalgautam6888 Thank you. Worked.

[@niteshwarsharma8595]

Hi sir i have a scenario i want to achieve using flow .. i have a checkbox field and whenever checkbox field gets checked i want to populate a date field . both these fields are on account object

[@ektachauhan9379]

Have you done that?

[@ektachauhan9379]

Having the same question on case object..I have to populate the field to show the date and time for the checkbox

[@niteshwarsharma8595]

yup

[@ektachauhan9379]

@@niteshwarsharma8595 howz?

[@PankajSharmaexplain]

BLUNDER

[@apexhours]

Let us know how we can improve. we would love to have your feedback

[@harpindersingh940]

@@apexhours Scheduled flow is implemented in wrong way and indeed would be a blunder if implemented in a real project. Flow will be executed for all Contacts matching criteria and then inside the Flow there is a Get Record element to fetch all matching contacts again and looping through those.

[@saikiran538]

Your way of teaching is good. But one thing you are lacking is you are very fast which is leading for mistakes and the new viewers will get confused. Please be little slower while explaining. All the best!

[@BugsbunnyEh]

explanation is good but he did not handle the requirement properly. the flow is completely wrong. schedule flow run for batch which mean each record will run one by one. u don't need to get again all the contact, its like a loop inside another loop. u can create account and use update the contact. so only need 2 element for the entire flow. yes performance is always need to concern when teaching.

[@chetsboy1]

Help needed Instead of adding condition in first comment I have created a decision component and adding the Condition record.accountId equal globalconstant.emptystring But it always running default path only. Even though soql showing there are contact records without parent account