Any known issue with Blackbaud Tiles?

Greetings friends.  Are there any known issues with Blackbaud Add-in tiles?  Last year, we created addin tiles for our product, 360MatchPro.  They were working forever but then stopped rendering in the web view all of the sudden.  In the console, I can see our add-in --- it's just not rendering on the page.




Then I see this in the network traffic



And in the console, there is a deprecation warning from the initiator in the second image above



Since our iframe is actually is still in the DOM and has always worked (until recently), I'm wondering if there are any know issues with Blackbaud Add-in tiles.  Any input would be appreciated.  


Thanks, and take it easy.




 

Comments

  • Michael Tims
    Michael Tims Blackbaud Employee
    Seventh Anniversary Kudos 2 Name Dropper Participant
    Hi Kanwei Li‍ !  I have your app connected to a test environment of mine and did a little debugging.  I do not see the `args.ready({ showUI: true, title:  '360MatchPro by Double the Donation'});` code being executed for your constituent tile add-in.  The `ready` callback would need to be called to inform the add-in host to show the add-in tile with the provided title.


    Can you please double check that the code surrounding `args.ready` is succeeding, to allow the callback to be executed?


    Thanks!

    -Michael Tims

    Blackbaud Software Engineer
  • Thank you for the prompt response - I think I'm getting close to figuring out what is happening. I'll get right back to you soon --- thank you!
  • Michael - you were right. The code surrounding args.ready was not succeeding for the addin-in in the gift entity.


    We have a rare case where two separate client accounts (same owner) were intentionally integrated into the same Blackbaud instances.  One of those accounts imports some of the records from the SKY API, and the other account imports the remaining records.  Before rendering the tile, we check the account to make sure the record was previously imported from the SKY API.  In this case, we'll have to check all of the accounts with an oauth connection to the same Blackbaud instance to see if any of those accounts imported the record.   Our add-in logic did not succeed because were checking for an imported record in only one of those accounts.  We've never had this problem because we've always had one-to-one relationships (each Blackbaud instance was integrated into exactly one client account).  


    Thanks a lot for looking into it -- very, very much appreciated!
  • Michael Tims
    Michael Tims Blackbaud Employee
    Seventh Anniversary Kudos 2 Name Dropper Participant
    Kanwei, glad you were able to track down what had changed!  Keep me posted if there's anything else I can assist with or test on my end.


    Have a great weekend!


    -Michael

Categories