#Accounts0 discussing

Hi @Rahul Fatnani  I did find the answer to this issue, although I wasn't happy with it but it does indeed make sense.  

According to Salesforce support: "To add, edit, or remove account team members , below permissions need to be present: Read on users AND Edit on accounts AND Account owner or above the owner in the role hierarchy (this third point is key).

This acts as the record sharing access and users who are not the account owner OR not  above the role hierarchy cannot add team members or can not see the access columns. This is because in the role hierarchy, users who are below the account owner cannot see those accounts as it will grant a higher level of access which would not be a good practice. 

 Hence user is not able to see the column for some records where he is not the owner of account or who is below in the role hierarchy."

Lastly, I found out on my own that if you give the "Log In As" permission to the user, that user will be able to see all four of the access columns. That is because the Log In As permission gives the user View All Data access. That type of access supersedes role hierarchy record sharing, thus the user has access above all account owners and can therefore see those columns. 

@Sandeep Thalluri & @Dimeta Jennings

Fyi. This is the real answer.  

基本的にはフローで設定することができますが、主従関係項目で変更を許可していない場合は変更できません。

質問内容を見る限りでは、取引先を編集しているとのことなので問題ないかと思います。

＜フローの例＞

レコードトリガフロー

1. 開始要素
   • オブジェクト：取引先責任者
   • トリガ：更新された
   • 最適化：アクションと関連レコード
2. レコードを更新
   • 方法：レコードを識別する条件を指定し、項目を個別に設定
   • オブジェクト：更新したいオブジェクト
   • 条件：
     1. 取引先責任者へのリレーション項目 次の文字列と一致する {!$Record.Id}
   • 項目：
     1. 取引先へのリレーション項目 次の文字列と一致する {!$Record.AccountId}

@Abhishek Pande Copy paste this below code and try to update contact.

Try to choose those contact whose Account have more than one Contact. Before Activating trigger keep Mailing Address blank

trigger updateContactAddress contact (after update){

        if(trigger.isAfter && trigger.isUpdate){

           set<Id> accountIdSet = new set<Id>();

            for(Contact con : trigger.new){

                if(con.MailingCity != trigger.oldMap.get(con.Id).MailingCity ||

                   con.MailingCountry != trigger.oldMap.get(con.Id).MailingCountry ||

                   con.MailingState != trigger.oldMap.get(con.Id).MailingState ||

                   con.MailingStreet != trigger.oldMap.get(con.Id).MailingStreet ||

                   con.MailingPostalCode != trigger.oldMap.get(con.Id).MailingPostalCode)

                {

                    accountIdSet.add(con.AccountId);

                }

            }

            System.debug('Account List= ' +accountIdSet);               

            list<Contact> conListToUpdate = new list<Contact>();

            for(contact conNew  : trigger.new){

                for(contact conOld : [Select Id, lastName, AccountId, MailingAddress, MailingCity, 

                                      MailingCountry, MailingState, MailingStreet, MailingPostalCode 

                                      from Contact where AccountId in:accountIdSet])

                {

                    if(conOld.Id != conNew.Id )

                    {

                        conOld.MailingCity = trigger.newMap.get(conNew.Id).MailingCity;

                        conOld.MailingCountry = trigger.newMap.get(conNew.Id).MailingCountry;

                        conOld.MailingState = trigger.newMap.get(conNew.Id).MailingState;

                        conOld.MailingStreet = trigger.newMap.get(conNew.Id).MailingStreet;

                        conOld.MailingPostalCode = trigger.newMap.get(conNew.Id).MailingPostalCode;

                        conListToUpdate.add(conOld);

                    }

                }

            }

            update conListToUpdate;

            System.debug('Updated Contact List = ' +conListToUpdate);

    }

}

Please mark this answer as best if it helps . Thanks

No, the standard Parent Account field can only hold a single AccountId, you can't concatenate Id's in a Lookup field like that.

For what you've described (an Many-to-Many object relationship) you would need to create a custom Junction Object 

 Documentation Create a Many-to-Many Relationship