Persistent Misconfigured Field Error

[Matt Sowden]

I'm receiving an error on Service Desk (Server) where I have a misconfigured field in a Request Type on my Portal. I found the Request Type in question, corrected the field, but it still states I have a misconfigured field.

I figured that it would go away, but it hasn't for months.

Finally I decided to just delete the Request Type and remake it, but still the Misconfigured Field error is persisting.

How do I get rid of that Error Message?

[Andy Heinzer · Accepted solution]

Hi Matt,

I don't recall seeing this kind of error in a Service Desk project.  Could you please let me know:

1. What version of Service Desk is this?
2. What this misconfiguration warning looks like? (a screenshot would be awesome)
3. Does this warning give you any specific details about the field name/type in question? 

I would be interested to try to recreate this problem in my own instance to better understand what might be causing this warning.

Thanks

Andy

[Matt Sowden]

Hi Andy,

1. The service desk version is 4.0.0 

2. I've attached some screenshots below!

3. Yes, check the screenshots (When you see them, please note that I've already deleted the Request Type that was giving the error, which means I have no recourse right now to try and fix this)

[Andy Heinzer]

Hi Matt,

If I understand your situation here, you have deleted the request type that is causing this warning to appear. 

However I am curious to see if you can click that link in the first screenshot to the 'fields' page.   My thought here is that perhaps you have another request type in question that might have the approvers field listed as both hidden and required.  If that happens, those fields need to have preset values or other wise the customers in the customer portal can't possibly complete the fields need to create requests.

Does that fields link take you to edit a different request type?  Or does it take you elsewhere?

Andy

[Matt Sowden]

That was it! It took me to another page with another completely different Request Type that had the same hidden field that was also misconfigured.

That's really strange! But, solved, so I suppose I can't complain too much. Thank you so much for your help Andy!

[Andy Heinzer]

Awesome, glad to hear that helped!