So it seems like the issue here is primarily one of Solomon Multi Company capability as it relates to CRM. It becomes a question of how you have Solomon set up. We communicate to Solomon at the object level and at the database level. Multi company support, in this scenario, comes by using the Solomon Multi Company module. All the companies are in the same app database and are distinguished by the company ID fields in the AR transaction. However, Solomon and CRM behavior differs in that Solomon shares all the customers in one table and all the customers and vendors are available to all the companies. This makes it impossible to distinguish which customer belongs to what company. With that said, a simple user-definable field on the Solomon customer record could make this distinction for us.

As you probably know, CRM associates all of its objects with Owners. And it is the owners/users that are in the different business units. So, if you were going to use CRM Business Units to distinguish each of the customers as belonging to different units/companies, then you would need to make sure that there is some indication on the Solomon customer record to associate ownership. Sometimes that is the Solomon salesperson field. In contrast, we have seen companies install multiple app databases for multiple companies. Today's version of Infuse has limited functionality to support the latter scenario. There is more to come as this is a developing story - but this is the situation as it stands today.