OAK!MERGE 14.4.7 for Sage ACT! was released today, it includes: 1. New export capability 2. Creates divisions for company hierarchy 3. Creates sub groups under groups 4. Exports record GUIDs 5. Uses GUIDs in Linking one entry to another 6. New transformations and more User with Version 14 or later can update for free. Users with earlier versions will need to purchase a version 14 license.
If a MY RECORD for an USER has a blank contact field; then NO updates to any record manager fields will occur. No error message is returned. This can also be described as ACT users must have Contact names Status: reproduced in 14.1 and 14.4 beta ACT! requires a contact name when you create a new user and does not let you errase it in the detail screen, but apparently there is someway to have a blank one. See below. Below has a space to illustrate how it looks.
The results of a merge are normally shown on the Results page. That page is an HTM page in the logs folder that can be reviews later. Know Bug: The HTM file may not be displayed after a large merge. The XML page is not properly processed to build the HTM results page. The merge was completed but the results were not displayed. This was due to a problem with the progress bar being displayed and was fixed in 14.3. Below is what is NOT displayed on some large imports on fast machines. Status: Fixed
October 27 to the 30th , 2011 at the Perfecting ACT! conference at the Scottsdale Plaza resort in AZ we demoed the new OAK!Merge 14.3 with export capabilities. Now in addition to importing, updating , and deleting info from ACT; you can export. The export capability is to dump out all the fields of an entire table to text delimited CSV. For example, the EXPORT feature will export all the contacts, notes, and history in 3 executions; one per table. The notes, history, activity EXPORTS all include the contact and company they are LINKED to. OAK!Merge must be installed on the same PC or network server as ACT! 2007 (Ver 9.0) or later including the Web Version
After a large import or some slower PCs, the final merge results page does not always appear. The Merge DID complete, but OAK!Merge could not display the results. OAK!Merge appears to be stuck. This was tracked to defect in the progress bar being displayed and was fixed in the 14. 3 beta release. It will be out in the 14.4 release.
OAK!Merge 14.1.0 is out of beta. It supports ACT 2012. Users of previous versions of OAK!Merge can get special upgrade pricing to move up to Version 14. Email firstname.lastname@example.org Version 14 also adds the new key words for $ROW$ $DATE$ $USER$. these are additional Reserved Key Words to $BLANK$ that was added in 13.3.3 to force a blank into a field. Key words are available for special situations to change the target field. They may be used in the source file as data or as a constant in the Mapping section. For text fields, the key words can be part of the string, but for date and numeric fields, key words must be exactly equal to the string. $ROW$ This adds the row number from the source file $DATE$ This adds current system date $USER$ This adds current ACT! user who was used as a log in to do the… read more →
OAK!MERGE 13.3.3 update is out. It includes a new look with new graphics and manual, new transformation features to BLANK target fields, support for Office 2010 Excel and Access and more…
OAK!Merge 13.2.0 is released. It includes the new Enterprise version, command line options for logging, and a bug fix for deleting records selected for deletion. The new Enterprise version includes the SalesForce Data Migration Kit for converting a SalesForce database into ACT! The command line options for logging allow users running unattended merges to select the logging level they desire for each merge. The Logging Level Switch is optional. The default level is “Full”. The default level will be used either when no level is specified or invalid level is specified. The 4 possible values are: None (or “0”) for “No Logging” Errors (or “1”) for “Errors Only” ErrorsWarnings (or “2”) for “Errors and Warnings” Full (or “3”) for “Full Logging” The new manual is also posted at OAK!Merge Full manual in PDF format (12 mb)
OAK!Merge 13.2.0 is out in limited release while we finish the documentation. It includes the new Enterprise version, command line options for logging, and a bug fix for deleting records selected for deletion. The new Enterprise version includes the SalesForce Data Migration Kit for converting a salesforce database into ACT! The command line options for logging allow users running unattended merges to select the logging level they desire for each merge.
Q: How do you delete Contacts from a database? A: Create a source file or do an ACT to ACT merge where you can match on one or more fields in the contact that will uniquely identify the contacts you want to delete. Usually Contact name, company name, and address would work well for example. The minimum is one matching field. Then, for execute options: select DELETE if they match and SKIP if they don’t match. Remember to do backup first, there is no “undo”; and always do a REFRESH after merges if you have the target ACT! database open. Note: there was a bug reported where the deleted contacts were not removed from ACT! This was fixed in 13.2.0