We have a Modal that contains two optional relationship fields (technically a third, but that one doesn't seem to be causing an issue like the others). When we start generating the content, we get the following GraphQL error: Cannot return null for non-nullable field.
There's an additional issue that we're seeing in these fields. If we edit the content, any of these relational fields that do not have anything selected will suddenly fill with a list of selections after tabbing/changing out of the browser tab/window and then back. Here's an illustration:
Before switching tabs
After switching tabs
Please note in the after image the Other Departments relational field. We did not make those selections. Those show up after changing windows or tabs.
@ttstauss thank you for the report. I'm adding this to our backlog to address soon. The second issue you mentioned is logged here, and I'll add it too.
We have a Modal that contains two optional relationship fields (technically a third, but that one doesn't seem to be causing an issue like the others). When we start generating the content, we get the following GraphQL error:
Cannot return null for non-nullable field
.Here are how the fields are set up:
Here is how ACM added the fields in the database:
When we run the following GraphQL query, we get the error (it's blowing up our GQTy based frontend):
Here is an example response (I added a test piece of content for purposes of this example):
Version information
Additional context
There's an additional issue that we're seeing in these fields. If we edit the content, any of these relational fields that do not have anything selected will suddenly fill with a list of selections after tabbing/changing out of the browser tab/window and then back. Here's an illustration:
Please note in the after image the
Other Departments
relational field. We did not make those selections. Those show up after changing windows or tabs.