How to avoid cascading changes in TFS?


I have just started using Visual Studio Team Services (team foundation server/TFS) to manage some of my NAV projects. 

Love it so far, and its free up to five users. Still a lot of challenges, but mostly PowerShell seem to be able to handle it. Several of my MVP colleges have made a lot of videos on YouTube about TFS and NAV Source code management that I can recommend. 

Source code control is actually just a small part of TFS. Its so much more. Like build-in bug and feature requests, testing and builds. 

But one thing that is a bit annoying when you manage Navision projects on source code level, is the cascading changes that happens when you change a field name. Don't know if cascading changes is the correct technical term. What I mean is if you change the field name, then every object in NAV, where this field is used, then the source is also changed. Despite the actual object does change physically.

So we end up with a lot more source code changes than actual changes!


Has anyone found a solution to this. 

Not doing it would of course be my own first response, changing the caption instead, but sometimes that's not really enough.

  • Hi Erik, didn't you know where to find me?

    Simplest way of doing this is: export all your objects into your workspace (using PowerShell) and TFS will check-out all the objects that have changed. Ideally this should only show the objects in your "cascade". The prerequisite is that before you started implementing this change in your NAV environment, code in NAV should have been synced with your TFS workspace (using PowerShell).
    This is the work I am doing on a daily basis.

    BTW: make it, that, before you checkin, you compare your pending changes with the latest version in TFS, to be sure that you checkin the right changes/objects.
Reply Children