Append vs AppendTo in Dynamics 365/ Dataverse / Dynamics CRM

[@MsKaryn]

THANK YOU! I was struggling with this and this was the most concise and clear explanation.

[@sumeetsatapathy7150]

Crystal clear explanation on Append & Append To. Thanks Sanjay.

[@Manover30]

Very helpful video, thanks for guidance

[@ohnmartun975]

Very good explanation for Append and Append To. Thanks Sanjay

[@swatibardapurkarnaik4546]

very helpful video thanks

[@jawadsidiqui]

Very well understood 100% you are the best mate

[@tristangeoffroy9286]

Thank you for this clarification, until now I was laisy and ticked all I could to make it works. :-)

[@katsut0shi]

thanks. great video

[@anug6837]

Really helpful....thank you

[@vellalalinganagarjunareddy2663]

Thank you. Nice video. Please make a video on N:N and 1:1 relationships in CRM

[@damudarling3467]

Nice

[@pmdci]

I noticed a very odd behaviour of Append / Append To in Dynamics 365 (8.2 on-prem) between users and Business Units. Seems like the minimum permissions to be able to create users in a BU (besides the create privilege for Users themselves) is Read and Append To for BU (without Append To, you will not see the New User button). However I noticed that users creating other users can create them in any BU as long as they can read the BU -- regardless of the Append To privilege. For example if I am about to create a user and I have BU Append To only at my local BU, but I can read BUs in the entire org, then I will be able to create the user in any BU. Also, there is no need for any Append privilege for the User entity.