GET Core Term API combines Term name and Description

@Stephen Boyle I wanted to suggest that the CoreTerm API be adjusted. Here is a screenshot of our Terms setup:

6aa2e75d6923b7ee1c41ff7e2ffbf49d-huge-im

You'll notice the term name and description are two separate values but there is a note saying it will display “Fall Term”.

When we leverage any of the APIs, we get this same output of “Fall Term”

However, if we us the Get a Single List API, the advance list will only give us the “Term Name” or “Fall” in this example

20b62d4bc5b368edd0a2d8db8b3e409e-huge-im

As you can imagine, as we try and join these tables, we are constantly having to code around dropping the “description” portion or adding “ Term”. Would it be possible to either update the CoreAPI to provide separate values and keep the combined output or to actually only bring down the term name? Even looking at the documentation, I should actually only get “Term” as it states it's bring the description:

Comments

  • @Stephen Boyle I found I could output a different column in my advance list to resolve this issue, so I'm all set. Unless you want to flag the API documentation to be updated. Thanks as always!

  • Stephen Boyle
    Stephen Boyle Blackbaud Employee
    Tenth Anniversary Kudos 5 Name Dropper Participant

    @Lindsey Bryant
    The list API returns the Advanced list as it is defined. It has no additional logic built in. So, the “displays as” label is true as far it goes when displaying the term in the UI somewhere. But b/c the list gives the fields individually, that is how the API outputs them.

    I'm glad you worked around the issue despite the difference.