locked
FilteringAttributes Not Stopping Plugin From Executing RRS feed

  • Question

  • We have a plugin that is fired when a contact record is updated.  We have set the FilteringAttributes in the register.xml file to contain 6 field names.  However, the plugin is firing whenever a contact is updated, regardless of whether one of the fields in the FilteringAttributes is modified.  Has anyone run into this before, and does anyone have a suggestion for preventing the plugin from firing if only fields other than the ones in the FilteringAttributes are modified?
    Monday, November 2, 2009 2:43 PM

Answers

  • Can you try to reset IIS to see if it works for you. Sometimes it gets cached. 
    Darren Liu | 刘嘉鸿 | MS CRM MVP | English Blog: http://msdynamicscrm-e.blogspot.com | Chinese Blog: http://liudarren.spaces.live.com
    Monday, November 2, 2009 2:44 PM
    Moderator

All replies

  • Can you try to reset IIS to see if it works for you. Sometimes it gets cached. 
    Darren Liu | 刘嘉鸿 | MS CRM MVP | English Blog: http://msdynamicscrm-e.blogspot.com | Chinese Blog: http://liudarren.spaces.live.com
    Monday, November 2, 2009 2:44 PM
    Moderator
  • Is there any reason why making an update through the UI seems to work fine with regard to the filtering attributes preventing the plugin from firing, but when an automated job does an update through the sdk crmservice.update method, the plugin fires even though none of the fields listed in the filtering attributes have  been modified?
    Monday, November 9, 2009 5:09 PM