MAJOR improvements include support for Single Sign On and a Native 64bit Version.
Note: Upgrade to the latest point release for TLS 1.1 compliance. Versions 2.20.32 and lower will return a login error if the Salesforce critical update "Require TLS 1.1 or higher for HTTPS connections" has been activated.
Upgrade Information
Starting in Version 2.2, PeopleImport now offers a 64bit and 32bit version. Please use the following matrix to determine which version to install based on the OS version type (32bit or 64bit) as well as the version of Microsoft Office running on the PC.
Notes:
- 32bit versions CANNOT be upgraded to the 64bit version
- Users installing the 64bit version with 64bit Office (full support)may want to uninstall the 32bit version once they have successfully installed the 64bit version, otherwise both will be installed on the PC.
- The 32bit version installs in the Program File(x86)\PeopleImport folder and the 64bit version installs in the Program Files\PeopleImport 64Bit folder.
- Users can upgrade (no uninstall required) from a previous 32bit version to the new 32bit version, and 64bit users will be able to upgrade to later 64bit versions (i.e. future releases).
As a precaution, please backup your PeopleImportData directory prior to upgrading.
Version 2.20.40 (released 6/22/17) is built on Salesforce API 39.0 (Winter '17). Any new Salesforce tables/fields/features added since API 35.0 (the version 2.20.39 was built on) will be available in this new release.
If a custom endpoint was specified in the previous version (e.g. to access a sandbox), after upgrading, the API version in the endpoint should be updated to 39.0.
New Features in PeopleImport 2.2:
- Login Support for Single Sign On
- Native 64bit Version Now Available
- Option to Change an Update to Insert
- If after reviewing the results a record is deemed to not be a good match users can simply "move" it to the Final Match step to be inserted vs. updated
- Error Message Added to the Final Results Files
- No need to check the logfile to determine why a record failed to be inserted/updated
Login Support for Single Sign On
PeopleImport now supports SSO (Single Sign On) using the NEW OAuth login option.
The standard Salesforce API Login is still available, but Salesforce OAuth Login with support for custom domains has been added. Users that do not use SSO can use either option for logging in, and those that use SSO will need to use the OAuth Login option.
More information on OAuth Logins and SSO can be found HERE.
OAuth Login generates a long term login token. If Auto Login is checked, the user will still be able to login EVEN IF THEIR SALESFORCE PASSWORD HAS BEEN CHANGED. When someone leaves the org it is recommended that their user license in Salesforce be immediately deactivated and/or their login token be revoked. If a "generic" user is being used to access PeopleImport, the password should be changed and the token should be revoked.
If an organization DOES NOT wish to allow OAuth Logins (i.e. long term tokens) the application can also be blocked completely. Users will still be able to use the API Login to access PeopleImport which does not allow logins with expired passwords.
User tokens can be revoked or the application can be blocked in Salesforce via Setup - > Manage Apps -> Connected App OAuth Usage
Native 64bit Version Now Available
PeopleImport now has full support for 64bit PC's. Not only will PeopleImport run on a 64bit PC, it can now utilize up to 32GB of RAM for faster downloads, building of the results grid, and greatly minimizes "System Out of Memory" exceptions.
Recommendations for running the 64bit version include:
- Minimum 8GB of RAM
- More RAM is recommended for users with millions of records up to a maximum of 32GB
- 64bit Microsoft Office (2010 or higher) is HIGHLY RECOMMENDED with the 64bit version for full support of all file types
- Office 2007 or lower available as 32bit ONLY
- csv and accdb CANNOT be read with the 32bit version of Office, unless running 32bit Office 2013 with the 64bit drivers manually installed (see "Note" below)
- Most other functions will work, but 64bit Office is HIGHLY recommended for full compatibility
- mdb files NOT supported, only accdb file
Note: The 64bit Version will support csv and accdb with 32bit Office 2013 as long as the 64bit Microsoft Access Drivers are manually installed. Office 2010 WILL NOT allow installing 64bit drivers with 32bit Office, but 32bit Office 2013 DOES allow the 64bit drivers to be installed. The 64bit Access Database Engine drivers can be downloaded here. When you click "Download" select "AccessDatabaseEngine_x64.exe" to install the 64 bit drivers. Users will get the error "The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine" if the 64bit drivers are not installed.
A 32bit version is also available for users running on a 64bit PC that still want/need the 32bit version due to not being able to upgrade to 64bit Office and/or smaller Salesforce orgs that do not need the extra RAM/processing power to complete their requests.
Not sure if you are running 32bit or 64bit Microsoft Office? Here are 2 ways to check:
- Using the "About" information:
- Office 2010: Open any Office document/program (i.e. excel, word, outlook) -> Click File -> Help. There will be an About section on the right and there it will indicate 32bit or 64bit after the Version #.
- Office 2013: Open any Office document/program (i.e. excel, word, outlook) -> Click File -> Account. There will be an "? About {program}" button on the right. Click the button and there it will indicate 32bit or 64bit after the Version #.
- Using Task Manager
- Open any Office document/program (i.e. excel, word, outlook) click Ctrl -> Alt -> Delete to bring up Task Manager. Click on the processes tab and check to see if (32 bit) (for Windows 8), or *32 (for Windows 7) is noted to the right of the application name.
Option to Change an Update to an Insert
In the event PeopleImport identifies a record as a match, but you disagree, the proposed action can be changed from Update to Insert. Simply right-click on the record (any column) and Move to Final Match. The record will be moved to the final match step to insert a New Lead or New Contact/New Account depending on the Final Matching Conditions specified in Step #3 - Matching.
The record will physically be moved to the Final Match Step in the grid and the overall Insert/Update Counts shown at the bottom of the results grid will be updated accordingly.
Error Message Added to the Final Results Files
No more having to go to the logfile to search for errors (they are still captured there also).
In previous versions if an error occurred when inserting/updating a record a generic message (e.g. Error Inserting Contact) was displayed in the Current Status field after processing. The user would then need to reference the logfile to determine the reason for the error. In the new release the Status column shown in the grid, and written to the Final Results and Final Results Dump files, now captures the error message shown in the logfile making it much easier to find/fix the errors and re-upload.
