• Limitation: When looking up a record or an address with a view to match on postcode, if the incoming postcode contains no space between its two parts (i.e. PH12LP) and the postcode in RE is formatted correctly (i.e. PH1 2LP), Blackbaud's SKY API won't allow us to ignore the space in the RE postcode to get a match. As such, matching on a postcode in this scenario is not possible, so may result in a duplicate address being added or the Matching Rule not finding the right record. It is worth highlighting that the inverse of that scenario will find a match (the incoming value has a space, but the RE record does not). Likewise, Importacular NXT's Record lookup will ignore text casing.

       

• Issue: Due to some restrictions within Blackbaud webview - you might find that Importacular NXT struggles to fit everything onto the screen. Sometimes resulting in multiple scroll bars.
  
  Interim solution: Make sure your screen is not zoomed in or out. Try and keep it at 100%. It works best on a screen with a resolution of 1920 x 1080.
  
  
• Issue: Some times, in Template Builder, you aren't able to drag and drop a mapping area on to the canvas whilst on Google Chrome
  
  Interim solution: Close your tab and open up a new one
  

• Limitation: Importacular NXT may appear slower than Importacular Classic. The main reason for this is to do with how Importacular NXT is able to lookup records. Blackbaud have provided developers two methods of looking up records. The first way is to look up by Constituent ID or by email address. This way is the fastest way to look up a record. The second way is to lookup by biographical fields, such as name and address. This way is much slower. Therefore, if your data does not contain a Constituent ID or it contains an email address that needs an extra field (such as first name) to reduce the lookup to one records, or you have a lot of matching rules in your Record lookup that match on biographical fields, it will take much longer for Importacular NXT to run through all your records and find suitable matches
  
  Remedy: We unfortunately cannot improve on what Blackbaud have offered, but we can help mitigate them a little. If you can, provide a constituent ID. If you are matching on email address, create one matching rule that matches on just email address and then create another matching rule to match on email address and first name (with equivalents). The first email matching rile should find all the records where the email address is only present on a single record quickly and the second email matching rule with help identify the right record when the email address is found on more than one address, albeit at a slower rate.