Two delete confirmation alert on contact and account record in CRM 2015

(0) Share

Report

Posted on by Nausher Sayeed

522

Hi,

I am getting twice confirmation alert when i click on delete button in contact and account entity record.

0121.Delete.PNG

I am using CRM 2015 onpremises version.

Any help is appreciated.

Thanks

Nausher

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (1)

Bas van de Sande 4,383 on at

Like (0)

Report

RE: Two delete confirmation alert on contact and account record in CRM 2015

Hi Nausher,

are there any customizations running on the entity forms or on the ribbon?

did you implement a delete yourself?

did you do something with cascading actions (change the relationship behaviour on the x-to-x relations --> e.g. set behaviour to referential )

Bas

Was this reply helpful? Yes No
Nausher Sayeed 522 on at

Like (0)

Report

RE: Two delete confirmation alert on contact and account record in CRM 2015

Hi Bas,

Thanks for your reply.

Yes, we have only implemented our custom delete button and uses CRM primary record delete command.

Nausher

Was this reply helpful? Yes No
Bas van de Sande 4,383 on at

Like (0)

Report

RE: Two delete confirmation alert on contact and account record in CRM 2015

Hi Nausher,

can you show the script you implemented in the custom delete button?

Bas

Was this reply helpful? Yes No
Nausher Sayeed 522 on at

Like (0)

Report

RE: Two delete confirmation alert on contact and account record in CRM 2015

Mcrm.Delete.PrimaryRecord is core command for the custom delete button. There is no such script.

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

RE: Two delete confirmation alert on contact and account record in CRM 2015

Hi

this is default in CRM to ask twice for mistake proof.

Was this reply helpful? Yes No
Verified answer

Nausher Sayeed 522 on at

Like (0)

Report

RE: Two delete confirmation alert on contact and account record in CRM 2015

This is CRM bug and it is resolved in CRM 2016.

Was this reply helpful? Yes No