The following mandatory fields are not filled in: (Empty)

Ricky S Larsson · ‎01-22-2019

What would be the first place to troubleshoot when there is an empty Mandatory field alert box? This shows up when I am trying to save a RITM after changing the state to Closed Completed. I'm logged in as Admin.

Is there a security rule hiding the field and thus not showing which field it is?

Ricky S Larsson · ‎02-01-2019

HI support created a problem out of this as the support guy I had contact with was able to successfully reproduce this issue in his own Out Of Box instance

The problem in our instance was that one variable was set to "Selection Required". The potential workaround was to:

- Un-tick 'Selection Required' on that Variable
- Use a Catalog UI Policy to set that Variable to mandatory
(The Catalog UI Policy must only apply on the 'Catalog Item view' (If it applies on the Requested Item the same error will occur)

I did this change in Test, moved it to Prod via update set and was about to try to close the task but all the tasks had been closed automatically so I don't know if this workaround helped or something else just fixed it.

View solution in original post

Sophia10 · ‎07-15-2019

Hi,

what did HI say? We have a similar situation, they get a similar error, "mandatory fields is not filled in: ,,,,,, " Bunch of , but no defined fields. We are kinda at a loss here, haven't found the issue yet :).

Br,

Sophia

Ricky S Larsson · ‎07-16-2019

The issue is when there are mandatory variable fields on the form (at least in our case)

On the form, where you get the ""mandatory fields is not filled in: ,,,,,, ", you need to check if you have any variables on that form. If you have:

- Go through each of them, and Un-tick 'Selection Required' if there is any variable that have that active.

- Instead of using 'Selection Required', create a Catalog UI Policy for that variable and set it to mandatory (It must only apply on the 'Catalog Item view' (If it applies on the Requested Item the same error will occur)

This was only a workaround on a problem that the development team was to work on, but I haven't heard anything else from them after that.

Hope this workaround helps!