locked
Merging of companies RRS feed

  • Question

  • Hi All,

    I have one requirement fro merging the company entity.

    My company entity will have projects mapped to it (the projects it was involved in). So searching for a company should list all the projects it was involved in. Now take the scenario as below

    -          Company A – 2 projects

    -          Company B – 3 projects

    -          Both merged and formed company C

    -          Company C – 4 projects

    When a search is made on Company C on how many projects they executed – the result should be 9 which is sum of projects executed by company A and B individually and as company C together.
    Similarly when a search is made on Company A on how many projects they executed – the result should be 6 which is sum of projects executed by Company A individually and as part of the merger under Company name C.

    Can any one guide me how to meet this requirement.

    Thanks in advance.
    Wednesday, October 13, 2010 1:10 PM

Answers

  • The second paragraph is just offering a mechnism to keep track of which company the project originated from. So if you have to know which Company had projects before they were merged then you could keep track of that on the Project entity itself. IT would require the same relatiohship added as you currently have accept the first relatioship you have need the relatiohsip behaviour set to Parental. The second relatiohship which you could add 'Original Company' would only require referential behaviour and no Reparenting. This is of course only if you need to keep track of which Projects belonged to various companies that get merged. Is it really necessary??
    MSCRM Bing'd - http://bingsoft.wordpress.com

    Check out the CRM 4 to CRM 2011 JavaScript Converter Tool
    Thursday, October 14, 2010 9:41 AM
    Moderator

All replies

  • Assuming Project is a custom entity with a relationship to Company (Account) then the relationship behaviour (i.e. you can view this by opening up the relationship in either of the entitys') has a setting for Reparent. If you set this to Cascade then all of the merged Company Projects will be moved across to the master Company. As the merge operation inactivates the merged Company you will not be able to see if it once had any Projects as these now exist against the master Company.

    To keep a history of the merged Company's PRojects you would have to create another relationship between the two entities called somehting like Original Company which shows on the Project form. The relationship behaviour should be set to Referential and Reparent to None.


    MSCRM Bing'd - http://bingsoft.wordpress.com

    Check out the CRM 4 to CRM 2011 JavaScript Converter Tool
    Wednesday, October 13, 2010 3:56 PM
    Moderator
  • Hi Rhett,

    Thanks for the response. I am clear with the first paragraph, can you please explain further about the second paragraph.

    Thanks

    Thursday, October 14, 2010 6:56 AM
  • The second paragraph is just offering a mechnism to keep track of which company the project originated from. So if you have to know which Company had projects before they were merged then you could keep track of that on the Project entity itself. IT would require the same relatiohship added as you currently have accept the first relatioship you have need the relatiohsip behaviour set to Parental. The second relatiohship which you could add 'Original Company' would only require referential behaviour and no Reparenting. This is of course only if you need to keep track of which Projects belonged to various companies that get merged. Is it really necessary??
    MSCRM Bing'd - http://bingsoft.wordpress.com

    Check out the CRM 4 to CRM 2011 JavaScript Converter Tool
    Thursday, October 14, 2010 9:41 AM
    Moderator