Arline, unfortunately not, but it's something we will be adding for the next release.
The connection string is defined in the IMan SageCRM user guide....it should be in form of:
http:///
Replacing Server with the server name or IP and CRM with the CRM instance (in capitals) per the IIS Application Name.
Closed due to inactivity.
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
Is there a way to test the connection string for SageCRM right when you create it?
That would help with troubleshooting. For example, there could be multiple points of failure.
EG should the connection string be
http://localhost/CRM/eware.dll/go
or
http://localhost/CRM/
?
Should the username/password be a named admin user dedicated to IMAN, or the username/password used to access SQL Server Mgt Studio tools for this database?
It would be nice to get an immediate test on setup.
Or...if there is already a way to test immediately, how do I do this?