Infuse Question # 6.3 Multi Company - Does is work?

In typical consulting fashion,  Yes and No.  Or ..... It depends.  

Out of the box, Infuse does replicate a multi company Solomon structure in CRM. There are several reasons for this, but the main reason is that CRM does not have multi company.  It does have the concept of Business Units, but that is entirely different than multi company. We can, and we have, integrated with multi company before. 

There are three scenarios for multi company in SL:

1) all in one application database

2) in multiple application databases

3) a combination of 1 and 2

Scenario 1: There needs to be some up-front design work done to understand what is needed from a multi company integration. Sometimes the CRM Business Unit concept can be used to fullfill their needs. In other cases, we just cannot do it with the way CRM is set up.  Somonon shares all the accounts between the companies.  It is orders and invoices that are the multi company part of Solomon, so there is nothing to "hook into" on customers to say they belong to one company or the other. We have used Sales person, account class, or even a custom field to control who owns the record in CRM and that person then would be assigned to different business units in CRM. This is as close as we get to muli company, and by far the most common scenario.

Scenario 2: This one is easier to accomplish. We simply install Infuse once for each application database.  Infuse is designed to integrate with two data sources (one for the CRM database and the other for a SL app database), so we need an instance of Infuse for each SL app database (they can all point to the same CRM). Although the process is a bit more straightforward, it does add overhead to the integration as you now have basically two integrations running. So the Scribe Server needs to be beefed up. Scribe can span multiple servers and will work efficiently in that type of environment.

  

 
Trackbacks
  • No trackbacks exist for this entry.
Comments
  • No comments exist for this entry.
Leave a comment

 Enter the above security code (required)

 Name (required)

 Email (will not be published) (required)

Your comment is 0 characters limited to 3000 characters.