Improved Scribe installation Guide!
Scribe Insight can populate Microsoft Dynamics CRM with key customer information from ERP, CRM, Web, and Legacy applications, making it possible for you to work with a complete customer profile. Scribe Insight is available with templates for leading applications and can be used to:
- Automatically feed leads into Microsoft Dynamics CRM from a Web site, telemarketing partners, or marketing campaigns
- Populate customers in Microsoft Dynamics CRM with financial and order history data from ERP
- Proactively monitor key customer activity through automated alerts sent to e-mail, cell phone, or Microsoft Dynamics CRM
- Enhance and validate data from third-parties via Web Services or data feeds
- Synchronize customer data in real time between Microsoft Dynamics CRM and other applications
A couple of days ago I did my first installation and migration with Scribe. The purpose behind this was to do a migration from Goldmine to Microsoft Dynamics CRM 3.0. It is a great tool once you get it working! Since I spend too much time deciphering the "readme" I thought to write my own speedy installation guide for Scribe when doing a migration from Goldmine, not sure if this would be applicable for other systems. Will update if needed.
- Download the latest version of Scribe
- Download the Goldmine to MSCRM templates
- Download the Scribe adapter for Microsoft CRM
- When installing on the C drive make sure you extract the Scribe download to that drive, so when installing to a D drive extract it to that drive!
- Install Scribe on the Goldmine server or do like I did, Install Scribe on the CRM server, install Goldmine and copy over the database that needs to be converted
- After installation add the crmadmin user to the "Scribe Console Users"
- Reboot
- Start the Scribe Workbench and register the product
- Install the Goldmine to Microsoft CRM templates
- Install the Microsoft CRM adapter. Use instructions mentioned at step 4. Choose option 1 in the setup after this run setup again and choose option 3
- Start the Scribe Console and add a new publisher, note the input queue
- On the Microsoft CRM server run the configuration utility (In Scribe program group) and paste the input queue you noted at step 11 as output queue
- Close the configuration utility
- Open Scribe Workbench and choose "File / Open" and browse to the Goldmine template directory. Choose template number one
- Test and import it. Do this for every DTS script in the Goldmine directory
I really liked the application and especially the results after migration. My recommendation to Scribe would be to write ONE new "Readme" so it will easier for new and existing users to migrate their existing data to Microsoft CRM.
Any suggestions or recommendations for my steps are welcome and I will update this "how-to". My Dutch friend has also some nice posts about Scribe...Take a look at them over here: https://friendlycrmonster.blogspot.com/2007/03/scribe-insight-vs-c360-import-manager.html and look on his blog for part 2 and 3.
Comments
Anonymous
April 23, 2007
Superb post Menno! I've quoted part of this article and pointed back to this site! Cheers.Anonymous
April 23, 2007
The comment has been removedAnonymous
April 23, 2007
Finally, you used it :-) And of course I agree Scribe Insight is very handy tool for all your data migration/integration.Anonymous
April 24, 2007
Menno blogs about this process quite well this week. "Scribe Insight can populate Microsoft DynamicsAnonymous
May 03, 2007
The comment has been removedAnonymous
May 22, 2007
I followed your instructions however I get an API error when I try to connect to the Goldmine Adapter object. Any suggestions? So far your instructions have been extremely helpful. Thanks.Anonymous
May 22, 2007
Rich, at what step are you getting this error and what is the exact message?Anonymous
May 23, 2007
I get the error when I launch the Workbench tool and open the first DTS package and try to configure the source using the Goldmine adapter. My config is a bit different as I installed this on my Goldmine Server (GM 6.7 SQL) as supposed to the CRM server. The specific error/s is Error # 104 "Error opening data source GoldMIne Adapter.Database." Source "ADP" Next error is Error # 384 "Goldmine API is not available or Goldmine may not be installed properly." Source "GoldMineAdapter" Any help would be appreciated. ThanksAnonymous
May 23, 2007
Rich, I believe you forgot step 11 and 12Anonymous
May 23, 2007
I did steps 11 and 12 and I just verified the settings. I'm trying now installing SQL 2000 on my CRM server and installing GM there as well with a restored DB.Anonymous
May 23, 2007
Rich, I think I remember what I did to solve this. Register the Goldmine gmcomapi.dll file (located in the Goldmine directory) using REGSVR32.exe. StartRun regsvr32 %goldmine path%gmcomapi.dll
Let me know if that helped.Anonymous
May 24, 2007
That did it! Thanks!Anonymous
May 24, 2007
Last question. Insight work great now that I can gain access to the GoldMine adapter. However I have several Custom Fields on the Fields Tab in GM and when I use the Goldmine adapter those fields are not visible in the objects available. Through an ODBC connection I can access them in the CONTACT2 table. The objects are the way to go as the links to the correct record id are there.Anonymous
June 28, 2007
Hi Rich, Here is the AB page on how to add custom fields to the GM Adapter. PROBLEM: Exposing custom fields in the Scribe Adapter for GoldMine so these fields can be mapped in data migration scenarios. RESOLUTION: Add the new field in the adapter metadata file (GoldMineAdapter.xml) and import the changed metadata using MetadataConfig.exe. Here is a detailed set of instructions. Login into GoldMine as someone with Master priveleges and Click FileConfigureCustom Fields... Find the field you need to add to the adapter and pull up the properties on it. Note the field length and the Name properties for the field. You'll need to duplicate these in the Adapter metadata file later on. Open GoldMineAdapter.xml into notepad or some text editor. Copy a FIELD to /FIELD tag out of the Contact object and then paste the copied portion in the list of fields for the Contacts object where you want the custom field to show in Scribe. Change FLD_NAME to the Name label from your field properties. Set the LENGTH tag value and set the NAME tag to a distinct name you'd like the field referred to in the Adapter. Save the metadata. Use MetadataConfig.exe to import your new metadata for the GoldMine Adapter. The next time you connect to the Contacts adapter object, the custom field will show in the field list where you placed the information in the metadata. ADDITIONAL INFORMATION: Customized fields in GoldMine are added to the Contact2.dbf file. The adapter collects fields from both Contact1.dbf and Contact2.dbf. It does this by means of the metadata stored in the internal database. Be sure save your Adapter metadata in a backup file so if there is a software update that affects the Metadata, the custom field can be added easily by importing this copy of the metadata containing the customized field information. Regards, BillAnonymous
July 17, 2007
I'm receiving the same error as above but for the ACT To CRM 3.0 adpater. I cannot find a dll to register for ACT in the files. Also, where do you download the Microsoft CRM 3.0 adapter? I did not notice one when I did the initial installation and just downloaded the adapter for ACT to Microsoft CRM 3.0. Any help would be much appreciated. The specific error/s is Error # 104 "Error opening data source GoldMIne Adapter.Database." Source "ADP" Next error is Error # 384 "Goldmine API is not available or Goldmine may not be installed properly." Source "GoldMineAdapter"Anonymous
July 18, 2007
The comment has been removedAnonymous
July 24, 2007
Hi, Is there any resource for help with Scribe? I am trying to update a control table in the source server upon successful integration and not quite getting it!! Vidya.Anonymous
July 24, 2007
Vidya, try calling them or look around on there help community portal.Anonymous
August 23, 2010
Dude - thank you - it rocks long and hard!