Which fields should not be updated for the main company and associates

Hello,

 

My understanding is that the name of the main company is tied to the license and should not be updated using the web services, is this correct?

Is this change automatically prevented by the API, or will it be applied and the license corrupted? (I don't dare trying to figure this out myself...)

Are there any other fields that are tied to the license and should not be changed?

What about the other companies added in Settings and maintenance > User > Our companies, should their name also not be changed?

 

Similarly, is there any field that should not be updated on a person that is an associate otherwise the associate would not be able to log in? Properties "Emails"? "Retired"?

 

Thank you for your help

 

 

RE: Which fields should not be updated for the main company and associates

Hello,

My understanding is that the name of the main company is tied to the license and should not be updated using the web services, is this correct?

Is this change automatically prevented by the API, or will it be applied and the license corrupted? (I don't dare trying to figure this out myself...)

You should never update the contact record that is tied to the license (see company table ownerContactId), it isn't prevented by the API so you will break the SuperOffice environment if you do, and will need International Support if you do it on Online.

Other companies that are marked as 'our companies' can be changed, those aren't tied to the license.

For associates, general rule of thumb is to not update any person record that is connected to an associate, especially not the email address since that can be used as username.

Av: David Hollegien 23. okt 2020

RE: Which fields should not be updated for the main company and associates

Hi David,

Thanks for your answer.

It's exactly what we do at the moment, we block any update to the main company and the associates. But our customers are frustrated not to be able to update the same fields as in SuperOffice.

In order to help them out, we would need to know exactly which fields should not be changed and if there is any uncertainty we will just not do it.

Av: Véronique Borel 23. okt 2020

RE: Which fields should not be updated for the main company and associates

Do not update the name of the owner company card in any way, no problem updating the department or the rest of the fields. Owner company is the first row in the ownercontactlink table, always.

Do not MOVE associates from a company found in the ownercontactlink table to a company card that is not

Email address is "free game" now that all CRM Online tenants are on SuperID

 

It's only when you use a system user that changes to this is allowed / not protected. Running in the users context the owner company should be protected as it is in the client. If that is not true, please let us know.

Av: Margrethe Romnes 24. okt 2020

RE: Which fields should not be updated for the main company and associates

Hi Margrethe,

Thank you for all this information, it is very helpful.

We do use the system user to create and update companies and persons, so I understand we need to be careful here.

Great that we can update email addresses for CRM Online, but I guess it means they cannot be changed for Onsite?

Av: Véronique Borel 27. okt 2020

RE: Which fields should not be updated for the main company and associates

Use of email address for login was only for login to CRM Online before SuperId.

Onsite have the username (associate.name) with the authentication info in Credentials (CRM5/Password or ActiveDirectory)

Av: Margrethe Romnes 27. okt 2020

RE: Which fields should not be updated for the main company and associates

Note: you can still login on OnSite using the email address on the person. So changing that is not recommended.

And since CRMScripts are running as system user when running in background tasks (ejSysUser), you can break your environment by updating the owner card.

Av: David Hollegien 27. okt 2020