Team Managed Service Project - Custom field with linked data displays in only one request

[Matthew Berzinskas]

I have a custom field in a team managed project called "Region". Its linked to a response on a form in one request, and it shows the options.

Another form/request using the exact same field displays "No Options". In the form it shows the options:

In the request it doesn't:

In the other form the options display as intended:

Does anyone have any idea what can be causing this? I've never come across inconsistencies in fields displaying in some requests and not others.

[Matthew Berzinskas]

Following up if anyone has any information or experience?

[Jeret Shuck]

I'm experiencing this issue on one of my forms as well. Have you found any workarounds?

EDIT: I managed to resolve this with the following steps:

1. Unlink the field from the form and save the form.
2. Add the custom field (in my case, it's a team-managed project's custom field) to the request type and save the edits to the request type.
3. Go back to the form, edit it, and re-add the field as a linked field.
4. Refresh the form on your support portal, and wala, a working linked field.
5. Profit!

It seems like this might be related to a new limitation where you can't have a "linked field" on both the form and the request type at the same time.  

However, after getting everything set up and working, if I try to make any further changes to the request type's field layout, I run into the same issue. I'm prompted with that "Remove field" message ^^

If I click "Remove field" as instructed, the field on my form becomes unlinked, which then results in the field displaying no options.

[Matthew Berzinskas]

Thanks, I will give this a try!