The advantages of using a dynamic value instead of a literal value (that you discuss starting at 9:50) would make a great topic for a Flowsome article and/or video.
Hey Melody -- thank you for the video! For clarification, although you have two contacts marked as "Direct" (at 6:16), ALL CONTACTS in this org are linked to their account(s) through the junction object Account Contact Relationship. Is that correct? Otherwise, in an org that was not set up to allow multiple accounts, you would need to loop through all contacts instead in search of the Account ID that triggered the flow. (Just thinking out loud here, but looking for confirmation. Thanks!)
Hi Neil, that is correct. Once contact to multiple account is enabled, all relationships will be created as ACR regardless of direct or indirect. It is also correct that if the org doesn't have contact to multiple accounts, we will need to loop through contacts instead of ACR, but we can still use find the contacts belong to a specific accounts using the account lookup field on the contact object. Hope this clarifies!
Hi Jason, what kind of duplicate error are you getting? Is it that you update the same record multiple time or you have duplicate records in your org? This might because your flow logic is conflicting with your duplicate rules, so I’d recommend modifying the flow logic so that the rules don’t get triggered
Hi there - So the Object is Account, however, the "Important" field is located in the Contact Object. I created the Important field in the Contact Object, however, I am getting a message "Enter a valid value". Do I need to create the "Important" field on the Account Object as well? Also, do I have to create "Account Contact Relationship" field as well? Thanks!
Hi Sharmila, this org is designed to have an important field on Account too, but you don't necessarily have to do it - as long as you use True/False values on the contact field:) Creating this field on ACR is not needed. Hope this helps!
