Is Microsoft barking mad? Have they lost any connection with reality? I just installed NAV2013 R2 on a three tier environment, just to find out that it's now impossible to alter tabledefinitions. That might be an error, you think, but no, it's by design...
We often develop at the clients' site. We simply take our notebooks, change the usercredentialstype to UserName, and are able to connect fine with both the database on SQL and the middletier. At our office, we have a lot of databases on the SQL Server, which have one (or sometimes two) middletiers. Our developers use these middletiers to develop. This is working great, doesn't have a lot problems, and is easy to administer. However, Microsoft has decided that this is not a good way to work, apparently.
In NAV 2013R2, they decided that it's necessary to validate the metadata when changing tables. I don't know why, but they might be right. However, to do so, the managementservice of the middletier is used. Great. I have a middletier, the managementservice is running, port 7045 is open, so no problem, right?
Apparently, the development environment does not have sufficient privileges the connect to the Microsoft Dynamics NAV Server and execute the validation.
The development.... Well, you get the drift.
The development environment and the middletier now need to be on the same computer. And that's not all: The developmentclient needs to be started elevated. then, and only then it's possible to change tables.
And true, it's all mentioned in the releasenotes (https://mbs.microsoft.com/downloads/cus ... lingTables
), and you might think this will be solved in the future. Well, think again. According to Microsoft, this is per design, and cannot be changed.
Are we the only one facing this problem, or are there more?