Finance | Project Operations, Human Resources, ...

Restrict Customer/Vendor Creation from front end

(0) Share

Report

Posted on by Community Member

I have a requirement to restrict Customer/Vendor creation/deletion from d365. if i click on New it should not allow me to create the customer/vendor.similar for deletion.

Actually we are going to create records with third party integration which should not be deleted, and new record should not be created from d365 side.

can any one guide me on how i can achieve this

I have the same question (0)

All responses (6)

Answers (0)

Sort by

Suggested answer

nmaenpaa 101,172 Moderator on at

Like (0)

Report
Copy link

Link copied!

I'm not sure if I understood the requirement. First you say "if i click on New it should allow me to create the customer/vendor.similar for deletion."

Then you say "Actually we are going to create records with third party integration which should not be deleted, and new record should not be created from d365 side."

Could you provide answers to following 4 questions (all of them, please):

1) Do you want to allow users to create customers/vendors in D365?

2) Do you want to allow users to delete customers/vendors in D365?

3) Do you need some special restrictions regarding deletion of customer/vendor that was created in from external system?

4) Should D365 users be allowed to edit/update customers/vendors?

Anyway, you can control create/delete possibilities via user roles, duties and privileges. There are no out of the box privileges that would allow updating of customer/vendor but not create/delete. As a rule of thumb the standard system provides you with two privileges: View or Maintain (full access). If you need to provide only Update access you need to create your own privileges.

docs.microsoft.com/.../security-privilege-properties

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

my bad."if i click on New it should allow me to create the customer/vendor.similar for deletion."

actually it should not allow.

Answers to questons :

1. User should not be able to create records directly in d365. once user clicks new or "ALT+N"it should throw error "create a customer from "third party application"".

2. User should not be able to delete records directly in d365. once user clicks new or "ALT+Delete"it should throw error "records created from "third party application" cannot be deleted".

3. there will not be direct records from d365, so technically all the records cannot be deleted.

4. edit /update will also be triggered from external systems mostly. but few records might be updated from d365 side as well.

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,172 Moderator on at

Like (0)

Report
Copy link

Link copied!

1 and 2 if you use the standard security framework, the New and Delete buttons and functionalities will be simply disabled. No error is thrown. I suggest to take this approach since that's how the security framework works.

If you want to throw some errors, you must forget about the security roles, and add your error throwing code before the standard create/delete methods in corresponding form data sources. For example in CustTable form, CustTable data source, create method (via Chain of command, throw your error before calling next). In this case nobody, even administrator, can create/delete records.

Was this reply helpful? Yes No
Suggested answer

Rahul Mohta 21,046 on at

Like (0)

Report
Copy link

Link copied!

just create a copy of std roles and remove the duty which allows them to manage customers and only give inquire only roles/duties

Was this reply helpful? Yes No
WillWU 22,363 on at

Like (0)

Report
Copy link

Link copied!

Hi ravishax,

So what you need is that users cannot do any operations on custTable in D365FO.

You could put the following codes in the OnActivated() eventhandler of form datasource.

custTable.allowCreate(false);

custTable.allowEdit(false);

custTable.allowDelete(false);

And put the codes that be used for alert in the OnCreating(),OnDeleting() eventhandler.

Was this reply helpful? Yes No
Suggested answer

SouravDam 11,732 on at

Like (0)

Report
Copy link

Link copied!

Hello ravishax,

As you mentioned that all these records will be pulled from a 3rd party application and then will be created in D365 automatically; therefore you can decide at what recurrence these records will updated in D365. It could be end of the day or in every 5-10 minutes depending on requirement of the client.

1. User should not be able to create records directly in d365. once user clicks new or "ALT+N"it should throw error "create a customer from "third party application"". --- I think no need to create any additional customization in this regard because you can simply control this through available standard roles and privileges in D365 as mentioned by Nikolaos.

2. User should not be able to delete records directly in d365. once user clicks new or "ALT+Delete"it should throw error "records created from "third party application" cannot be deleted". --- This is same as the 1st point. Can be controlled this through available standard roles and privileges in D365.

3. there will not be direct records from d365, so technically all the records cannot be deleted. --- Whatever the applications you are using to bring all these data in D365 from the 3rd party application; simply set the recurrence as highlighted above. Therefore; whenever you are creating, updating or even deleting any such record in that 3rd party system; D365 will be automatically updated based on the recurrence as you set.

4. edit /update will also be triggered from external systems mostly. but few records might be updated from d365 side as well. --- Same as point no. 3

Kindly check and let us know for any further concern you have on this.

Best regards,
Sourav Dam

Kindly mark this thread 'Yes' if this is answered your query which may help other community members in this forum.

Was this reply helpful? Yes No