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) / 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

  • Community Member Profile Picture
    Community Member on at
    RE: One Plugin for an entity firing for other entity ?

    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

  • Sainath Pillanagrovi Profile Picture
    Sainath Pillanagrovi 217 on at
    RE: One Plugin for an entity firing for other entity ?

    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
    RE: One Plugin for an entity firing for other entity ?

    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

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

🌸 Community Spring Festival 2025 Challenge Winners! 🌸

Congratulations to all our community participants!

Adis Hodzic – Community Spotlight

We are honored to recognize Adis Hodzic as our May 2025 Community…

Kudos to the April Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard > Microsoft Dynamics CRM (Archived)

#1
Mohamed Amine Mahmoudi Profile Picture

Mohamed Amine Mahmoudi 83 Super User 2025 Season 1

#2
Community Member Profile Picture

Community Member 52

#3
dkrishna Profile Picture

dkrishna 6

Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans