Hi Dave

Thanks for your feedback, but I'm still stuck...

I have updated the save synctree method and also think I have corrected the pathArray.

As per the screenshot below shows the tree with the "default" and "special" tag group nodes having an id of "tagGroup-default" and "tagGroup-special" respectively.

My updated code is

$scope.save = function (cmsTags) {
        TagManagerResource.save(cmsTags).then(function (response) {
            $scope.cmsTags = response.data;             
            var pathArray = ['tagGroup-'+cmsTags.group];
            pathArray.push(cmsTags.id);
            navigationService.syncTree({ tree: 'TagManagerTree', path: pathArray, forceReload: true, activate: false }).then(
                function (syncArgs) {
                    if ($routeParams.save) {
                        $location.path(syncArgs.node.routePath);
                    }
                });

            notificationsService.success("Success", "'" + cmsTags.tag + "' has been saved");
        });
    };

Any suggestions please ?

Thanks

Nigel

NB I can look into the window.confirm later - trying to tick the above off first. :-)

Have just checked routeParams object that there was no "create" so have changed this to the following:

 $scope.save = function (cmsTags) {
        TagManagerResource.save(cmsTags).then(function (response) {
            $scope.cmsTags = response.data;
            var pathArray = ['tagGroup-' + cmsTags.group];
            pathArray.push(cmsTags.id);
            navigationService.syncTree({ tree: 'TagManagerTree', path: pathArray, forceReload: true, activate: false }).then(
                function (syncArgs) {
                    if ($routeParams.method == "edit") {
                        $location.path(syncArgs.node.routePath);
                    }
                });

            notificationsService.success("Success", "'" + cmsTags.tag + "' has been saved");
        });

As you can guess I am guessing at what is the problem, but still no joy... :-(

OK, partly sorted due to an epiphany in the night - have updated the code to below and the tree now stays expanded. Just gotta figure out how to reload the node data after save - it is still disappearing.

 $scope.save = function (cmsTags) {
        TagManagerResource.save(cmsTags).then(function (response) {
            $scope.cmsTags = response.data;
            var pathArray = ['-1', 'tagGroup-' + cmsTags.group];
            pathArray.push(cmsTags.id);
            navigationService.syncTree({ tree: 'TagManagerTree', path: pathArray, forceReload: true, activate: false }).then(
                function (syncArgs) {
                    if ($routeParams.method == "edit") {
                        $location.path(syncArgs.node.routePath);
                    }
                });

            notificationsService.success("Success", "'" + cmsTags.tag + "' has been saved");
        });
    };

In doing a bit more debugging I have now realised the variable '$location' isn't defined as per the previous code snippet.

As per the Umbraco2014 sample the opening 2 lines of code are as follows:

angular.module('umbraco').controller('UmbUkFest.Speakers.EditController',
function ($scope, $routeParams, $location, speakersResource, dialogService, entityResource, mediaHelper, notificationsService, navigationService) {

I simply do not understand how the variables are constructed / passed to the function.

Didn't read the rest of this thread, but wanted to give you a heads up on your latest reply that the variables are passed to that function via dependency injection.

That is, Angular looks at the names of each parameter, and based on the names it will try to find a service matching that name so it can instantiate it and pass it to that function.

As an example, the "$location" service is a built-in service that will be passed to that function. You can also create your own services and they will follow this same pattern of dependency injection.

And just to be clear, not every function gets parameters dependency injected. Typically, you would do this in controller functions (like the one you have in your latest reply).

Hi Nicholas

Appreciate the feedback and clarification of how angular works.

Cheers, Nigel

So finally "hacked" my way to solving the reload issue. Found some code on another post (https://our.umbraco.org/forum/extending-umbraco-and-using-the-api/79436-reload-node-in-custom-tree) which detailed a $route.reload() method being called.

So added $route to the controller and updated my code as follows and now working fine.

    $scope.save = function (cmsTags) {
        TagManagerResource.save(cmsTags).then(function (response) {
            $scope.cmsTags = response.data;
            var pathArray = ['-1', 'tagGroup-' + cmsTags.group];
            notificationsService.success("Success", "'" + cmsTags.tag + "' has been saved");
            pathArray.push(cmsTags.id);
            navigationService.syncTree({ tree: 'TagManagerTree', path: pathArray, forceReload: true, activate: false }).then(
                function (syncArgs) {
                    if ($routeParams.method == "edit") {
                        $location.path(syncArgs.node.routePath);
                        $route.reload();
                    }
                });
        });
    };

Onto the custom dialog as suggested by Dave

is working on a reply...