Question Re: Code List Restriction only on creation in CRM and CX Q&A

Code List Restriction only on creation

Former Member — Wed, 16 May 2018 07:12:26 GMT

Dear all,

we would like to restrict the CREATION of Accounts with the role "Customer" for a user group. But EDITING Customers (adding a phone number etc.) should be possible. The respective CLR correctly hides the "Customer" Role in the dropdown menu on creation, but also prevents editing the object later.

Any hints would be appreciated.

Regards, Martin

Re: Code List Restriction only on creation

amit_kumar159 — Wed, 16 May 2018 08:10:40 GMT

Dear Martin,

Code List restriction for Account role should not prevent the editing object. I have tested in our internal system and it is working correctly.

Role field dropdown is not showing the value 'Customer', eventhough if you uncheck the prospect field, system takes role as customer but system will not allow to save and throwing below error message:

Entry Customer for Role field not consistent as per Code List Restriction. Please contact your system administrator.

So if you using CLR for Account role customer and creating account with role prospect but later system is allowing to change the data after creation.

Re: Code List Restriction only on creation

Former Member — Wed, 16 May 2018 08:55:48 GMT

Dear Amit,

thank you for your answer.

We have two different account roles: "customer" and "prospect". A certain user group should not be able to create customers, but only create prospects. However, they should be able to edit prospects and existing customers later (for example: add a phone number - and leave the role unchanged).

Can this be done with CLR?

Thanks!

Martin

Re: Code List Restriction only on creation

Former Member — Thu, 17 May 2018 08:03:33 GMT

Hi Martin,

Like Amit mentioned above the purpose for Code List Restriction is to restrict the value of drop down we should not mix this with authorisations

Regards,

Bejoy

Re: Code List Restriction only on creation

Former Member — Fri, 28 Sep 2018 07:19:00 GMT

If anyone cares: the final solution was to change/"lower" the message severity > inform, but let users save changes.