Supporting the Solomon Project Series: SEEKING BETA SITES
A recurring question to us has been, "Are you going to come out with integration to the Solomon Project Series?" and "Do you support Solomon Project?" The answer is yes and yes.
This is what we are thinking —- 2 basic designs:
Design 1 -
In Solomon, the Project ID is part of the AR Docs, SO header, and a few other tables. We are able to extract Project IDs from SL; the question is what to do with them. CRM does not have a project entity. So something is going to have to be set up. Basically, we can build a very simple custom entity called "Project" which can then be easily linked to invoices and orders that are replicated into CRM from SL. This basic configuration would allow us to review all the orders and invoices that are being billed aginst a specific project. The custom entity can then be used to hold project metadata that Solomon does not. Things like e-mails and appointments can also be linked to these projects using a very basic custom entity.
Design 2 -
Not only create a custom CRM entity for Project, but include the ability to pass the Project IDs back to Solomon for Work orders that come out of CRM. So when a service activity happens, you can then pass it back to Solomon for billing on a specific project. We can support this without customization to our Infuse Service since we can push the Project ID with orders.
We are actively seeking some Beta sites to help drive this design. So if you know of anyone who is looking to integrate the Solomon Project series with CRM, definitely let us know.
This is what we are thinking —- 2 basic designs:
Design 1 -
In Solomon, the Project ID is part of the AR Docs, SO header, and a few other tables. We are able to extract Project IDs from SL; the question is what to do with them. CRM does not have a project entity. So something is going to have to be set up. Basically, we can build a very simple custom entity called "Project" which can then be easily linked to invoices and orders that are replicated into CRM from SL. This basic configuration would allow us to review all the orders and invoices that are being billed aginst a specific project. The custom entity can then be used to hold project metadata that Solomon does not. Things like e-mails and appointments can also be linked to these projects using a very basic custom entity.
Design 2 -
Not only create a custom CRM entity for Project, but include the ability to pass the Project IDs back to Solomon for Work orders that come out of CRM. So when a service activity happens, you can then pass it back to Solomon for billing on a specific project. We can support this without customization to our Infuse Service since we can push the Project ID with orders.
We are actively seeking some Beta sites to help drive this design. So if you know of anyone who is looking to integrate the Solomon Project series with CRM, definitely let us know.



Comments