Using Project Server 2013, when attempting to open a particular project in Project Pro, we are getting the dialogue box saying “The enterprise global already contains a view named “No Group”. Do you want to replace the view with the one from the enterprise global, replace all items with duplicate names, rename the view in the project, or cancel opening the project?” If we select “replace”, we are prompted several more times, 7 to be exact, with the same dialogue, then in the drop down menu for Group in the View Tab, we see the option for [No Group] listed 7 times. We have checked the enterprise global to confirm there are no local tables or views polluting the enterprise global. Does anyone have a clue as to why this is happening?
Dave, great question. The short version is that you have a view in your local global as well as your enterprise global. Project Server manages artifacts (views, tables, filters, groups, etc.) and creates a problem if the enterprise global has a duplicate name in your local global. It’s hard to explain in a forum response but it is affectionately called polluting the enterprise global. I did a quick search (Project Server polluting the Enterprise Global) and found this article, but there are many more: http://blog.epmainc.com/understanding-how-local-views-can-pollute-enterprise-global/
The short answer is to never create an enterprise view of the same name as a local view. Hope that helps…
Thanks, Larry. I had seen those articles and double checked to confirm that there are no local global artifacts in the enterprise global. Any other possibilities?
Unfortunately no. That’s the behavior when you have duplicate artifacts. Your example is a view named “No Group”, is that correct? Assuming you are correct, then my only thought is that you may have a corruption someplace. I’m also assuming it is happening with everyone and every project.
You could try restoring the global. Not sure how large your organization is or how many projects, but it will only happen once for each project (the easy way out). Wish I could provide more help, but maybe someone else has something to try.
Thanks, Larry. Correct, the view in question was called “No Group”. Oddly, it was only happening on one project and a couple people, but not to me. Instead of clicking “replace” like I mentioned we did in my original post, I have since selected “rename” the duplicate “No Group” views, then delete them, “Save As” locally, then replace the enterprise project with the local version. So far, that seems to have eliminated the issue, but still a mystery as to what the root cause was. Thanks!
Good to hear. Hopefully it won’t come up again. If it does then something is wrong with that view. My next suggestion would be to delete the view in both that project and any and all globals, and then recreate it.