We see this a lot when we publish plugins through the plugin deployer. We don't tend to notice this as we most of the time user Parent pipeline. But why there is another Pipe Line.
The reason for this is simple.
If you open the entity from CRM without going to it from another CRM record this would be the parent pipe line.
If you go to the same entity record through another entities record it would be the child pipe line.
If you have written a plugin for a particular entity and have used the parent pipe line then it would not fire id the same scenario happens if you have to come the record through another record.
There is a very nice article about this written in the following web link. This helped me too to understand the difference. This was given to me by a colleague of mine.
http://crmscape.blogspot.com/2009/02/ms-crm-40-plug-in-stages-pipelines-and.html
The reason for this is simple.
If you open the entity from CRM without going to it from another CRM record this would be the parent pipe line.
If you go to the same entity record through another entities record it would be the child pipe line.
If you have written a plugin for a particular entity and have used the parent pipe line then it would not fire id the same scenario happens if you have to come the record through another record.
There is a very nice article about this written in the following web link. This helped me too to understand the difference. This was given to me by a colleague of mine.
http://crmscape.blogspot.com/2009/02/ms-crm-40-plug-in-stages-pipelines-and.html
No comments:
Post a Comment