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

[David Sloan]

You can see that I configured it a week ago.

[David Sloan]

I am starting to think that this is related to a view rule I created. If I go to Project > Projects > All, I am looking at the projects list from the Default view. If I click on an individual record, it gives me the OIT view because of a view rule I set up. Then if I try to click Configure Related Lists (or Configure Form Layout does the same thing) it gives me that message. Perhaps I didn't set things up correctly with the view rule? Or is this a bug in Orlando?

[David Sloan]

Hmmm, though the view is in a scoped application, my view rule that forces it is in the global application. Could that be causing this problem?

[Willem]

Can you deactivate this rule and try again? I think you are right and this is a good candidate for the cause.

[David Sloan]

Yes, it works fine if that rule is deactivated. I created that rule in the global scope because pm_project is in the global scope, and as far as I can tell, it is not possible to create a view rule in a scoped application for a table that is not in that application. But the view was created within the scoped application. Should I remove that view from the scoped application and recreate it in global? And if so, can I do that by exporting the XML, removing the sys_package and sys_scope data, and then importing the XML, or is that a bad idea?