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

Announcements

Introducing our New Video Series: Community Spotlight
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / One Plugin for an enti...
Microsoft Dynamics CRM (Archived)

One Plugin for an entity firing for other entity ?

(0) ShareShare
ReportReport
Posted on by Sainath Pillanagrovi 217

Hi All,

I have plugin on EntityA and it is  triggered on 3 events which are setstate,setstatedynamicEntity,update so it has 3 SDK steps and logic for this is  whenever a EntityA record is deactivated/inactivated its related entities are also deactivated.

I have a another plugin on EntityB and it is triggered on update of a field so Update single SDK Step  and logic for this is to do some calculations substraction and create a record and deactivate its related records.

So now the problem is when a field is updated on EntityB 

EnitityA plugin is firing for EntityB with update message not sure with this strange behavior

I have checked  there is no relation between the 2 entities and they are from different modules

pastedimage1568809898013v1.png

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    Community Member on at

    Hi,

    So if I understood correctly, when plugin from EntityB is fired, it also fires plugin for EntityA, correct?

    You say that on plugin of EntityB you deactivate its related records. Those related records/entities are EntityA? Because if they are, you are deactivating EntityA so the plugin(s) step(s) that are triggered by statuscode or statecode are being fired (maybe). My suggestion is to take a look of those related records and the filtering attributes of steps of EntityA.

    Best regards

  • Sainath Pillanagrovi Profile Picture
    Sainath Pillanagrovi 217 on at

    Thanks for your response

    Entity B related records are no where related to Entity A

    They are from different modules and has no relation

  • Community Member Profile Picture
    Community Member on at

    Did you do some debugg to check which fields are coming on the update message? If not, I would recommend you to do so. Then go to EntityA (on system customization) and check the dependencies on the attributes updated. To check if there are plugin steps, workflows, etc that are updating those attributes.

    Because it seems that the update on EntityA comes from something made on plugin of EntityB. That plugin can fire someting on EntityC and then on EntityC there is something that can fire EntityA. I do not know the complexity of your system but do some trace work to check where that update comes from :)

    Cheers

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

News and Announcements

Introducing our New Video Series: Community Spotlight

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the June Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans