web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Bulk edit changes the ...
Microsoft Dynamics CRM (Archived)

Bulk edit changes the record status and triggers workflow

(0) ShareShare
ReportReport
Posted on by Community Member

I select multiple records in a view, click edit and change a field by the bulk edit tool. Besides the field it also changes Status of all modified records. More precisely, it fires a change of Status (from Active to Active). And it triggers a workflow bind to a status change, although there is no real status change.

I found only one source briefly mentioning this without any explanation:

The status code changes when a user does a bulk edit for any records from view within a custom entity without manually changing the status code in CRM Online. This is by design.

https://blogs.msdn.microsoft.com/emeadcrmsupport/2015/10/26/dynamics-crm-bulk-delete-general-support-questions/

My questions are:

  1. Why is this by design? Why does it happen?
  2. Is there workaround for the workflow to trigger only on a real status change (Activation, Deactivation)?
  3. We use CRM 2016 OnPremise. Is this new in 2016? We haven’t noticed this earlier.

*This post is locked for comments

I have the same question (0)
  • Verified answer
    a33ik Profile Picture
    a33ik 84,331 Most Valuable Professional on at

    Hello,

    It is by design because Microsoft decided that it is good idea. If you don't want to have this functionality open Suggestion item on Connect portal. I'm afraid that your possibilities are limited.

  • Community Member Profile Picture
    Community Member on at

    Hello, thank you for your ideas. Should I understand that as it is not possible to handle it in a workflow? I can imagine workaround in a plugin, but probably not in workflow.

    I am very skeptical about Connect. I entered about 20 suggestions last year with 1-6 upvotes, covering suggestions, non-critical bugs and translation mistakes. None of them was Fixed or commented, although I try to write them very precisely and I always check for duplicates.

    Usually, only chance is to start a support ticket. But if it is stated as by-design, though very illogically, they are not going to help me. At least, I’d like to know the reason to be able to explain this to the customer.

  • Suggested answer
    a33ik Profile Picture
    a33ik 84,331 Most Valuable Professional on at

    I'm skeptical about Connect as well. We have event a joke about Connect like "Ticket won't be fixed. It would be just closed". So I 200% understand your pain.

    I had an idea about code workaround but I didn't knew your background so you can try following trick - that can work only in on-premise (luckily you are):

    1. Create a plugin that will handle Update operation of your entity and register it outside isolation.

    2. Add reference to System.Web assembly.

    3. Use HttpContext for analysis of source where your plugin was initiated from and if it is Bulk Editing window - just remove statecode/status code from list of fields that were changed.

    There are no guarantees that it would work but this is direction that you can go trying to solve your issue.

  • Community Member Profile Picture
    Community Member on at

    Thanks for the idea, it is interesting. I was thinking of pre-update plugin checking the old and new values in statecode and statuscode. If they are same, nothing happens. If they are different, workflow is triggered (directly, or thru a field change). However, customer does most of the customization on his own and has no plugins so far. But it is another story.

  • Community Member Profile Picture
    Community Member on at

    Hi

    We are facing this same issue in 2016. was a fix found for this or did Microsoft respond with any reasoning?

    This is a big oversight by Microsoft and is causing one of our clients major issues, which may result in them not upgrading.

    Kind Regards

    Bradley Ash

  • Verified answer
    Community Member Profile Picture
    Community Member on at

    Although, earlier stated as by-design, it seems this issue is solved in CRM 2016-1

    Bulk edit on entities causes the Status Reason Field to change back to the default value.

    https://support.microsoft.com/en-us/kb/3154952

  • Community Member Profile Picture
    Community Member on at

    Thank You Jiri, after deploying the update this resolved our issue :)

  • Community Member Profile Picture
    Community Member on at

    Hi Guys,

    I am facing a similar issue in CRM 4.0, while doing bulk edit, the status revert it to back to original value. Is this concern residing in CRM 4.0 also.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans