Support Center

Updates not happening in Destiny - Status 72 errors in the siflog

Last Updated: Nov 30, 2015 01:29PM MST

Symptom:

Updates are not happening to Patron records
siflog.txt is full of Status=72 errors

  • siflog.txt location: (Destiny application machine: Destiny Installation Directory:Follett\FSC-Destiny\jboss\server\destiny\log\siflog.txt)
  • example error:  2015-05-06 08:45:15    INFO     SifFacade    ()    Unexpected code returned=PatronUpdateReturn[ status=72 ...


Issue:

Currently, when the setting within Destiny is enabled to “Require District ID for patron records”, the Destiny application will not update records unless that data is part of the event.  

With SIF, only the data that changes is sent in an event. The District ID is only included via SIF on an add (new student), a sync (collects all mapped student data), or if the DistrictID itself changes.  Follett is aware of this aspect of SIF and will be making adjustments to the Destiny application's processing of SIF events in a future release.

Workaround:

As a workaround, you can disable the setting to “Require District ID for patron records”.  Making this change would allow all of the change events to process, and you should see transfers, data updates, etc happen as expected.

To make the change in Destiny:

Log in as the District Administrator, click “Setup”, click “Edit District” (the pad and paper at the top on the far right), and uncheck “Require District ID for patron records”, and click “Save”.

 

 

 

 

 

 

 

support@kimonocloud.com
http://assets2.desk.com/
false
desk
Loading
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
about
false
Invalid characters found
/customer/en/portal/articles/autocomplete