7-Dec-2016: Required actions in regards to the new transaction categories

As you should know from our previous announcement, the transaction categories will change in the upcoming release of version 1.11.0. In this article we want to inform you about the actions that may be required from your side regarding this update.

If your application and/or database has stored/mapped the values of one or more of the following fields of the Category Resource:

  • id
  • name
  • parentId
  • parentName
  • children

then you must be aware that one or several of these values might change with the new version of finAPI. In this case, you should make sure that your application/database uses the updated values, otherwise you might get unexpected behaviour (for instance, because you're trying to request a category by an identifier that no longer exists, or that is now pointing to a different category).

If your application and/or database has stored/mapped the value of the following field of the Transaction Resource:

  • category

then you must be aware that this value might change for a transcation with the new version of finAPI. This can mean either that the category changed to a different category, or that the transcation doesn't have a category anymore at all (i.e. category field is null). Here you should make sure your application/database uses the updated values as well.

As long as you don't have any of the above mentioned fields stored/mapped in any way in your applicaiton or your database, then no action is required from your side.

 

 

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk