Many to Many and Junction Object

Поділитися
Вставка
  • Опубліковано 7 вер 2024
  • Hope this video helps you in understanding junction objects, it was definitely a confusing topic for me when I started. In this video, we will look at examples and use cases for many to many relationships and how Junction objects help support that. We create a custom junction object and also look at some standard "junction" object in Salesforce. This is from my experience and building Data Models.
    Here is the help doc that I talked about: help.salesforc...
    and a trailhead on this: trailhead.sale...

КОМЕНТАРІ • 23

  • @spikenjam
    @spikenjam 3 роки тому +2

    It's so nice to see a tutorial done in Lightening. Thanks for the time you took to make this. Well done :)

  • @anthonyokolie4578
    @anthonyokolie4578 Рік тому

    You are a star, Pratima!😂

  • @Kaltinril
    @Kaltinril 2 роки тому

    Great video, thank you! You went over everything. I came here trying to figure out how to make the ID field go away so I don't see it, but instead, see the related table's values. Thank you!

  • @RutlandSquad
    @RutlandSquad 2 роки тому

    Thank you for the great description! It helped us with our business processes.

    • @PratimaShri
      @PratimaShri  2 роки тому

      Awesome! I love hearing that 😊

  • @sanketkarpeSparkiEe
    @sanketkarpeSparkiEe 3 роки тому

    You are super fast at delivering things we ask you! Thank you for this superb video and this was really helpful❤️❤️❤️❤️

    • @PratimaShri
      @PratimaShri  3 роки тому +1

      Thank you, keep them coming, I get to them whenever I can! Glad it helped you! :)

  • @danielsbwebb
    @danielsbwebb 3 роки тому

    Thanks Pratima - this helps me explain to my team the need to J.Objects for our use case of study groups with multiple members and members who could be in multiple study groups. Have a great week!

    • @PratimaShri
      @PratimaShri  3 роки тому

      Lovely Thanks! Have a great week

  • @oleeejek
    @oleeejek 2 роки тому

    That's a good explanation of the concept. Thanks

  • @ip7590
    @ip7590 2 роки тому

    Thank you for explaining this. Great work. Really enjoyed this

  • @macbradf
    @macbradf 3 роки тому

    Thanks so much for this thorough walk through. It was super helpful!

  • @user-hk8cm9kl4o
    @user-hk8cm9kl4o 3 роки тому

    Thanks a lot, Pratima. Excellent material for me. I wish you success in your work!!!

  • @JaimeBIDtravel
    @JaimeBIDtravel 3 роки тому

    Pratima, this was an awesome explanation, very clear. Actually I love the Salesforce standard junction objects as Contact Role as they do not have "name" or "auto number" which is not needed at all. On the other hand, I am trying to create a many to many relationship for accounts with the standard "AccountContactRelation" object, as I am using person accounts. But when I link one person account with another one, in one record the account related list gets populated but in the other record gets populated the contact related list. It seems that in my case, I have to deal with two related list on the same page, I guess, unless I use some custom development. If you have ideas to sort this out, I would truly appreciate. Thanks!

  • @sanketkarpeSparkiEe
    @sanketkarpeSparkiEe 3 роки тому

    Hi Pratima,
    Can you please explain us more about conversation of lookup to master detail and vice versa

  • @arpanlidder5076
    @arpanlidder5076 2 роки тому

    Can you make a video on health cloud party model? Enjoyed this one.

    • @PratimaShri
      @PratimaShri  2 роки тому

      Party model? Not sure what that is. I have future plans on making more video on health cloud data models

    • @arpanlidder5076
      @arpanlidder5076 2 роки тому

      @@PratimaShri thank you for responding. This was something oracle/siebel made popular. A way to model many to many relationships like a Household. Party and Party relationships

  • @sushmitasensharma5401
    @sushmitasensharma5401 2 роки тому

    Can you tell me the answer to one scenario: Let's say the user has access to one Master object (let's say the primary one) and the access to the junction object, then will the user be able to see the secondary object's records as well?

    • @PratimaShri
      @PratimaShri  2 роки тому

      If they dont have View access to the object itself, then they shouldn't be able to see that other object. in terms record visibility, it will depend on both Masters settings on relationship, best way to know would be create it in dev org and see :) May be this doc will help: help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm&type=5