General Ledger Post Journal Entry Validation Issue - Record marked inactive

Barton Dyson
Barton Dyson
Fourth Anniversary Kudos 1 Name Dropper Participant
in Blackbaud Financial Edge NXT® APIs

As part of a project for a customer, we are creating journal entries using the Sky API POST JOURNAL ENTRY endpoint. In some cases, either transaction codes or transaction attributes that need to be used are marked as inactive, which prevents the endpoint from saving and generates an error. We trap that and notify the user which record needs to be activated. At that point, a user is editing the record in database view or web view to mark as active. Once the change is made, we are able to immediately verify that the record is now active in NXT by viewing the tables section. When the process is run again, 5 hours later in one case, the batch validation in API still shows an error and says the record is inactive, preventing save. The last error happened Friday, failed again 5 hours after activating the transaction attribute, but ran successfully this on Monday.

Is this expected behavior? Are batch validation items cached for performance reasons or is this some type of error with the POST JE API?

Comments

Categories