Why do I get a "The view has not been configured" message when the view has been configured?

[David Sloan]

I have a form that I created within a scoped application. This view has its own form layout, list layout, and related lists. If I am looking at record in that view and try to configure Related Lists, I get a message that the view has been configured and an option to clone the "Default view" to "OIT" (my view name), but I know the view "OIT" already exists. In fact, I can say "No" and then switch to OIT in the "View name" dropdown on this form for configuring related lists. If I am already on the OIT view for the form and already seeing the related lists I previously configured for that view, why does it want to create a new view here?asks me if want to clone the "Default view" to "OIT," but as far as I can tell the "OIT" view has already been configured. If I

[Willem]

I would stay away from xml manipulation. Best option is to remove the view from the scope and recreate in global in a update set in the global scope. Let me know how it goes 🙂

[David Sloan · Accepted solution]

The problem was much simpler than I had realized! It turns out that my view rule was pointed to OIT (all caps), which was the title of the view named oit (all lower case). ServiceNow recognized that it should use the oit view when it didn't find a view named OIT, but when trying to configure the view, it would look for a view named OIT and scream that this view was not configured. I changed the "view" field of my view rule to all lower case, and this solved the problem.

[Willem]

Oh man, devil in the details! Great you found it and thanks for sharing! 🙂