Skip to content

John

My feedback

1 result found

  1. 34 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    John commented  · 

    I want to add that we believe this to be a bug in the API

    An error occurred while saving the comment
    John commented  · 

    Presently the API for posting manual journals accepts tracking categories and options only by name using the "Name" and "Option" fields. It allows the "TrackingCategoryID" and "TrackingOptionID" fields to be entered and the API even validates that the format of these entries are properly formed GUIDs, but doesn't use them to determine the Category or Option to be applied.
    The issue here is that the user can rename the existing Categories and Options and that breaks the interface unless you know that you need to update these also in your application; using the GUIDs overcomes this as it is a unique identifier and is not dependent on getting the names exactly right.

    John supported this idea  · 

Feedback and Knowledge Base