nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Constituent records being created with first name value duplicated in job title field

Jonathan White

I'm creating constituent records via the API endpoint POST `/constituent/v1/constituents`

The records created via the API show the first_name value in a field labelled "Job Title" in the "Bio 1" information page in the admin interface. The first_name value is correctly stored but the job_title field seems to copy the first_name value.

If I edit the first_name value in the interface, only the first_name field is updated.

The result is the same if I include a job_title property in the posted data or not. The endpoint reference docs make no mention of a job_title field so I'm not sure why my create requests are putting anything in the job_title field at all.
https://developer.sky.blackbaud.com/api#api=56b76470069a0509c8f1c5b3&operation=CreateConstituent

Does anyone know how to set or update the Job Title property?

Find more posts tagged with

Comments

Alex Wong

@Jonathan White
What do you mean by:

"Job Title" in the "Bio 1" information page in the admin interface

Bio 1 tab makes me think you are talking about database view of RE, please confirm.

Assuming it is Bio 1 tab in database view, there is no “job title” field there neither. Though it is possible that your database admin “renamed” one of the field as “job title”. So please send some screenshots to help you further

Jonathan White

@Alex Wong, thanks for your response.

Below is an image of where the Job Title field appears in the interface. I'm not especially familiar with the interface myself so I'm not sure what's default and what's custom.

I have to obscure the personal data but you would see the same value in the First name and Job Title fields after creating the record.

a04b1000469dc40c090abda4672400fc-huge-bi

Alex Wong

@Jonathan White

Your screenshot is correctly call the database view (might want to remember this for future use so others can understand you)
that “Job Title” field is a “renamed” field. The original field name is “Nickname”.

Nickname in database view is the same as “Preferred name” in webview.

in API, you can set the preferred_name property to change it.

Alex Wong

@Jonathan White
Not sure if you are the database admin, if not, you should discuss with the db admin on “reverting” customized field to its original. As the webview DOES NOT honor the customized field name. Meaning right now in your RE instance, on the webview, what your org consider as job title that they had added, is now showing up on the webview as “Preferred Name”

Imagine the confusion:
John Smith
Preferred Name: Accountant

Jonathan White

@Alex Wong, thanks again for your help.

That would explain what I'm seeing. I am setting the preferred_name property with the same data as first_name.

I'm not the DB admin. I've only taken on the task of sending data into the application via the API. I will make mention of it to the DB admin but I assume there is some reason the field has been renamed. I'll likely just have to make note of that for future reference.