API returning NULL for form label


#1

Starting last week Monday (Feb 26, 2018), we started seeing NULLs for the source-label property of a field on the contact record. No change was done to the forms as far as I know. It just started happening

Here's an example of a contact that filled out a couple different forms, one from November 8, 2017 and one from March 2nd, 2018. This is happening on all forms in the the system.

The actual contact as an example and API call we use is https://api.hubapi.com/contacts/v1/contact/vid/30824657/profile?hapikey=XXXXXXXXXXXXXXXXX (minus the API key of course)

    "question1": {
        "value": "15 Year of experience",
        "versions": [
            {
                "value": "15 Year of experience",
                "source-type": "FORM",
                "source-id": "10e252c9-3fa8-4fca-a6da-7f974a9a9458",
                "source-label": null,
                "timestamp": 1519949663429,
                "selected": false
            },
            {
                "value": "15",
                "source-type": "FORM",
                "source-id": "b3b6a792-c4cc-4c15-9b95-df455bbc7030",
                "source-label": "How many years of experience do you have?",
                "timestamp": 1510108620835,
                "selected": false
            }

Any thoughts of what's going on?


#2

Hi @cbrasel,

Can you give me your Hub ID so I can take a closer look at the contact you mentioned?


#3

Hi @Derek_Gervais, it's 605296.


#4

Hi @cbrasel,

Thank you for your patience here; I've taken this issue to my team, and we've identified the issue on our end. I'll continue to work with them on rolling out a fix, and I'll update this thread when I have some more information. In the meantime feel free to reach out here with any questions or concerns.


#5

Thanks, Derek. I appreciate it.

Cory


#6

Hi Derek,
Any updates on from the team on this one?

Thanks,
Cory


#7

Hi @cbrasel,

Not just yet. We've identified the issue, but haven't yet rolled out any fix. I'll keep you posted via this topic when I have an update on the status of the fix.


#8

Hi @cbrasel,

Sorry for the long wait here, this topic slipped through the cracks. This is now fixed (and have been fixed for a while). Let me know if you have any other questions.