OAK!MERGE 15.5.1 for Sage ACT!

Posted on March 15, 2013October 14, 2016 by oakadmin

OAK!MERGE 15.5.1 and SalesForce Data Migration Kit 15.5.1.0 for Sage ACT! was released today 1 Fixed bug in custom table export to include links to Contact and Company 2. Revised and improved wording on progress page: step 1,2.3.4... 3. Use CTRL F to find columns in the Mapping page See previous posts for other Version 15 updates Users with earlier versions will need to purchase a version 15 license. Users with Version 15.0 or later can install 15.5 over the existing installation wi...

Posted on October 22, 2012 by oakadmin

OAK!MERGE 15.3.0 for Sage ACT! was released today, 10/22/12, It includes: Added Priority field as a mappable field to Activity table Updated SalesForce Data Migration Kit mappings and profiles Updated manual for SalesForce Data Migration Kit ver 15 Added shortcut to SalesForce Data Migration Kit to the Start menu in OAK!Merge program listing Added semi-automatic mode option to the SalesForce Data Migration Kit menu Added future activities attached to the Opportunities for SalesForce Da...

OAK!MERGE 15.2.0 for Sage ACT!

Posted on September 23, 2012October 14, 2016 by oakadmin

OAK!MERGE 15.2.0 for Sage ACT! was released today, 9 /23/12, It includes: 1. Bug Fix for allowing profiles and maps to be selected and not selected for use. See previous post for other Version 15 updates Users with Version 15.0 or 15.1 can update to 15.2 for free and will not have to reactivate . Users with earlier versions will need to purchase a version 15 license. Users with Version 15.0 or later can install 15.2 over the existing installation without having to reactivate. downl...

Q/A mappings vs profiles

Posted on July 24, 2009 by oakadmin

Question: can I use field mappings in any version of OAK!Merge? Answer: yes, field mappings are included in Basic and up versions. Note: In the Basic version you can save and use mappings. This is not the same as saving and using profiles. Mappings are only the field mappings. The profiles include the mappings AND the log-in/password, type of source and file name. Profiles are required for unattended automated merges. Profiles are not included in Basic. If you create and reuse field...