In This Article:

    Advanced Import Resolution Queue

    In This Article:

      Recent software enhancements are shown in red.

      During import, Salsa CRM analyzes Advanced Import file data for whether the data update existing records or duplicate existing records. Post-import, all data are sent to the Data Import Resolution Queue.

      To access an import's resolution queue, select the Tools > Data Sync > Resolution Queue menu.

      Date fields at the top of the screen help to restrict your search to certain dates on which you imported data. You can also restrict the search to just successful imports, as opposed to imports that have not completed yet.

      ResQueue.png

      Imported Data Sync to Engage

      If you want to send an email blast, you may want to know where to go to see if your data has synced with Salsa Engage. Salsa CRM checks for data import rows in all Resolution Queues that have a Success status and need to be synced to Engage. A regular process in Salsa CRM is always running to check for imported data that needs to be synced to Engage. This process will then send in-bulk any imported data that hasn't been synced every 18 minutes via a Long Running Process called "Sync staged supporters with Engage".

      Resolution Queue Details

      When the Data Import window opens, double-click on the date of the import for which you wish to process data records. The Data Import Resolution Queue opens in a new browser tab for that particular import. Depending on the size of the import file, you may see a progress bar that indicates the progress made in loading the data rows.

      Details in the Data Import Resolution Queue indicate to you if a row of imported data was imported successfully, or if anything could have delayed the import, such as duplicating existing information or potentially updating existing information. Those scenarios are described in detail below under the Potential Duplicate and Constituent Update section headers.

      Constituent Update

      Constituent Number in the incoming dataset is the trigger to update existing records. CRM users must act to confirm acceptance of any Constituent Update

      Incoming Constituent Number values that match existing Constituent Number values place the data rows into the Resolution Queue as a Constituent Update status. The following steps allow you to either confirm records as new constituents or update existing constituent records.

      1. Open the Data Import Resolution Queue.
      2. Double-click a record with the Constituent Update status.
      3. The Resolve Constituent Update window opens. This window allows you to compare the existing information to that which you are importing, to make sure the right Import ID or Constituent Number was used for that record.
        AI_Resolve_Const_Update.png
      4. If you select an Add New option for any data point, the incoming values will be added as new, primary values. Once you have made your selections, select the OK button.

        PRO TIP: The bottom of this window also allows you to, with one click of the button, Update Existing All, Use Existing All or Ignore Changes.
      5. Once you select the OK button, a Message window will appear. This window will alert you to the successful update and include the Constituent Number. Select OK.
      6. The Status of the record will reflect as Success. This indicates that the existing record has been updated.

      Potential Duplicate

      For potentially duplicated records, Salsa CRM compares the following fields of the record that is being imported against the information already contained in your database:

      • First two letters of the First NameAND
      • Entire Last Name, AND
        1. Address Line 1 is empty, OR
        2. First 3 characters of Address Line 1

      OR

      • Email Address

      OR

      • Government ID

      Any match of incoming data places the data row into the Resolution Queue as a Potential Duplicate status.

      WARNING: Because the import checks only the first two letters of the First Name, the following scenario is possible, where an incoming record is a Potential Duplicate of an unintended constituent:

        First Name Last Name Address Line 1 Email Government ID
      Incoming record... Christopher Jackson <blank> <blank> <blank>
      Potentially duplicates... Chantal Jackson <blank> <blank> <blank>

       

      Use the following steps to import the record as a new constituent or update an existing constituent record.

      1. When the Data Import Resolution Queue opens, double-click on a record with the Potential Duplicate Status.
        ResQueue_Details.png
      2. The Resolve Potential Duplicate window opens. This window allows you to compare the existing information to that which you are importing, which may be a duplicate of an existing record.
        Resolve_Potential_Duplicates.png
      3. The top panel allows you to select the information being imported so that you can Add as a New Constituent. This option will automatically create an entirely new constituent record based on the information contained in the file you are importing.
      4. The second panel allows you to Choose Existing Salsa CRM Constituent. Selecting this option will “activate” the lower panels so that you may view the existing information and choose whether to update the existing information, use the existing information or, for certain fields, Add New information.  
      5. If you select the Add New options, the constituent record will have an additional address and/or phone number added to the record and marked as Primary. Once you have made your selections, select the OK button. The bottom of this window also allows you to, with one click of the button, Update Existing All, Use Existing All or Ignore Changes.
      6. Once you select the OK button, a Message window will appear. This window will alert you to the successful update and include the Constituent Number. Select OK.
      7. The Status of the record will reflect as Success. This indicates that these updates have been made to the existing record.

      Unknown City

      Address Line 1, City, State, and Postal Code are all required in the incoming data set in order to provide a valid address record. Salsa CRM stores the combination of City, State, Postal Code, and Country in its own table in order to make city definitions consistent for all data entry users (Mt. Lebanon versus Mount Lebanon, for example).

      When the Automatically Add New Cities setting is unchecked on the Import Options panel, cities that are not already in the database are not automatically added. Users should review these cases, for example, if there was a misspelling in the source data.

      Invalid or Missing Data

      If you are presented with the Invalid or Missing Data status, some expected information for one of the data columns was not included.

      1. Select that row from the Resolution Queue; the Edit Advanced Import Data Row window will appear.
      2. The top of this window will display the Error Message; fields listed below the error message will display in pink if that field needs to be edited. You can edit the field directly in this window.
      3. Once you have made the necessary changes, select the OK button.

      Other Resolution Queue Statuses

      Duplicate Data Sync Map—The unique Import ID for this constituent is the same as another "unique" id submitted by the same vendor.

      Duplicate ID—Another constituent has already been stored with the same SSN.

      Ignore—There was absolutely no change to an existing record by incoming data intended to update an existing record.Missing Record—A Donation pointing to a constituent record has been imported, and that constituent does not exist.

      Missing Parent Record—The referenced SSN, Import ID, or Constituent Number no longer exists in the database.

      Pledge Pay No Installments—A pledge payment arrived but no installments are defined to link to this payment.

      Pledge Pay No Template—A pledge payment is noted in the import data, but no pledge template was set up for this payment.

      Success—This entry was successfully imported into Salsa CRM.

      System Error—An error occurred while processing this row. Typically this is only resolvable by contacting Salsa support.

      Unprocessed—Typically, a temporary status that displays immediately after loading an import.  As each row is processed, this status changes to its final status.

      Donation Update—This status is for information purposes only.  Donations cannot be updated via Advanced Import.

      Resolve All

      NOTE: When you select the Resolve All button, this will update all of the matching records in Salsa CRM all at once. THIS CHANGE CANNOT BE UNDONE.

      1. Select the Resolve All button at the bottom left of the Data Import Resolution Queue screen; the Resolve All pop-up will appear.

        AI_Resolve_All_Button.png
      2. On this pop-up, you will select one of the items to resolve all records with that status in this queue. For instance, if you have chosen to Resolve All of the Constituent Update statuses, the Resolve Constituent Update window will appear.

        NOTE: The selection you make here will affect every record in the queue with the same status. If you choose to update existing records, every corresponding constituent record will be affected in the same way by this update.
      3. Click OK.
      4. The Confirmation Required pop-up will appear. This is to warn you that all of the records in the resolution queue with the selected status will be updated using the options you have selected. This operation cannot be undone.
      5. Click OK.
      6. After you have selected OK, select the Search button to refresh the screen. If the Success filter at the top of the screen is not selected, you will see any remaining statuses to be addressed.

      NOTE: If Salsa CRM finds more than one record that could be a potential duplicate, it cannot choose which one to update. Therefore, those records will not resolve and change to a Success status. Those will have to be resolved manually.

      PRO TIP: Resolving All Constituent Updates and Potential Duplicates produce Long Running Processes in the database (Tools > Long Running Processes) that work behind the scenes to update data. Check that menu to see when your processes complete. Once these processes complete, then the Engage Sync Long Running Process will start. 
      AI_RQ_LRP.png

      Was this article helpful?
      0 out of 0 found this helpful
      Have more questions? Submit a request

      Comments

      0 comments

      Article is closed for comments.