This tool is used to manage all NAV versions in use (similar to existing tools such as DynamicsNAV protocol handler) but advanced in its behavior and built with around a central sharepoint list of databases. I could think of having these in separate repos too, but I’am not sure if this would be overkill.įor Interacting with NAV (Importing/Exporting source code, tracking changes, etc) I extended our tool that we use internally. This however might change, if anybody has another idea or can think of an issue with this, please tell me about it! The reason for this was mainly the complexity of NAV versions that inherit from each other (W1 -> Local -> Local ISV -> Customer Solution) We can separate these in Repositories while still maintaining their links through remotes.įor different Versions of ISV Solutions (NAV2009, NAV2013, NAV2013R2, NAV2015, …) we will be using different branches. So this year we finally had time to do so.Īfter lots of thinking and testing and analyzing of our workflows we decided to use Git as our source control system and Team Foundation Server for Project Management. And I for myself wanted to use a SCM (Source Control Management) for quite some time. I was so busy at work and had to deal with some personal issues (health) and didn’t bother about blogging that much…Īnyway lot’s of things happend, I gave up (at least for now) on the compare tool i was creating, it was soo time consuming and almost ate up all of my spare time, and since we got the Application Merge Utilities from Microsoft, the need for this is not that strong as it used to be.īut eventually i will use it (or parts of it) in other projects.īut for now the big topic is Git!! I’am not the first one blogging about it, git and source control in general (TFSVC for Example) was all over the place. Have fun with security and permissions, and mostly Dynamics NAV! If you need further assistance contact us.įor more Dynamics NAV tips and tricks, and support articles click here.It’s been a veeeeery long time since my last post. If you miss this step, it is possible that all users with this permission will be impacted with this restriction. Remember to make a copy of the permission or permission set and apply this to those users only applicable to this restriction. Table Filter (When you do AssistEdit on the highlighted field) In order to get this result, there are some setup changes that you will need to do.Ģ. As per the restriction already placed, this report won’t show me any other data but the ones that I have a permission to view, which is the items that has Base Unit of Measure=BOX. When I run this report, I only see the three items that I see on my Item List view. There is no filter applied to this report. Let me run the Item List Report to ensure if this change is applied to my reports as well. There is no filter applied to this screen. I am in Cronus Canada and this is my list view after applying this restriction.Īs you can see, I don’t see any other items where Base Unit of Measure=BOX. Let’s say that I only want to show the items on my Item List (or my user’s) where the Base Unit of Measure is BOX. This is done by setting a Security Filter on the Permission Page. Can I limit what a user can see on screen? I get this question quite often from many of our Microsoft Dynamics NAV clients and the simple answer is yes, you can.