• 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. I is worth highlighting that the inverse of that scenario will find a match. Likewise, Importacular NXT's lookup will ignore text casing.

  • Issue: When that Card appears in the Imports Requiring Attention section, all the records have not pulled across and viewing the results section is incomplete

    Interim Solution: Wait until all the records have been processed before viewing the results

  • Issue: When cloning a Record Lookup in Template Manager and then seeking to edit it, the 'Return to Template Builder' button doesn't work.

    Interim Solution: just click out side of the window to return to the Template Builder

  • Issue: When dragging and dropping a mapping area on to the Template (we call it the canvas), the screen can pull you to the bottom righthand side of the screen. The more mapping areas you have can result in pushing the Primary Constituent Mapping Area off screen.

Interim solution:  Whilst still holding the Area Mapping, pull it back to the left-hand side Area Mapping menu and back on the the canvas. This should re-centre things. Also, look to recentre your template using the button that has four arrows pointing out:        

  • 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% 

  • 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