【Flow】|【Practice】| Update Parent From A Collection of Child Records

แชร์
ฝัง
  • เผยแพร่เมื่อ 5 ก.ค. 2024
  • Visit our blog for more Flow knowledge:
    salesforce-flowsome.com/
    【Related Posts】
    Update through Account Contact Relationship: salesforce-flowsome.com/updat...
    【Credits】
    Music: Daily Beetle, Life of Riley by Kevin MacLeod are licensed under CC BY 4.0
    - Source: incompetech.com/music/royalty-...
    - Source: incompetech.com/music/royalty-...
    - Artist: incompetech.com/
    #salesforce #flow #practice #salesforceFlowsome

ความคิดเห็น • 16

  • @cgirl001
    @cgirl001 2 ปีที่แล้ว +2

    I have been trying to figure out how to do this for a week. SO glad I came across this video tonight! THANK YOU Salesforce Flowsome!

    • @salesforceflowsome
      @salesforceflowsome  2 ปีที่แล้ว

      I am so happy that this helped! Good luck with all the future learning and building!

  • @neilhohmann10
    @neilhohmann10 2 ปีที่แล้ว +2

    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.

    • @salesforceflowsome
      @salesforceflowsome  2 ปีที่แล้ว

      Great idea Neil! I will add this to my idea box:)

  • @amyutkan
    @amyutkan ปีที่แล้ว

    had to listen a few times to get it! so cool!

  • @chrisuttley984
    @chrisuttley984 2 ปีที่แล้ว +1

    Well done. Very clear.

  • @SalesforceHowToSeries
    @SalesforceHowToSeries 11 หลายเดือนก่อน

    Hey Melody, thank you so much for your video. But how do we go about this if the field to update is a picklist?

  • @neilhohmann10
    @neilhohmann10 2 ปีที่แล้ว +2

    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!)

    • @salesforceflowsome
      @salesforceflowsome  2 ปีที่แล้ว

      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!

  • @grimreaper_650
    @grimreaper_650 ปีที่แล้ว +2

    I need to update child accounts from parent account how to get all child accounts record and update a field on those child record

  • @sharmilajennas3469
    @sharmilajennas3469 2 ปีที่แล้ว +1

    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!

    • @salesforceflowsome
      @salesforceflowsome  2 ปีที่แล้ว +1

      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!

    • @sharmilajennas3469
      @sharmilajennas3469 2 ปีที่แล้ว +1

      @@salesforceflowsome Thanks again...I will try.

  • @jasonspencerphiladelphia
    @jasonspencerphiladelphia 2 ปีที่แล้ว +1

    Great video but I'm getting a duplicate error. Any way to filter them out?

    • @salesforceflowsome
      @salesforceflowsome  2 ปีที่แล้ว

      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