Add DeleteTopNavigationNodesDefinition / DeleteQuickLaunchNavigationNodesDefinition to delete navigation nodes

[SubPointSupport]

M2 should be able to hide / delete quick and top navigation nodes based on criteria:

• all of them
• some of them by Title or Url match

This feature was highly desired by the community. Should be implemented in the first place.

[ghost]

Because the IsVisible property does not work as expected because of a SharePoint bug, an easy way to remove Navigation nodes by Title or Url match would be a modification of QuickLaunchNavigationNodeModelHandler: Instead of setting the IsVisible property to false, we could remove the navigation node.

[SubPointSupport]

Thanks for the input, @markusjenni.

We'll go with a new definition similar to DeleteWebPartsDefinition. The goal is to separate deleting operation avoiding mixing up creation / update process and potential data losses. M2 always creates or updates stuff, deleting is extremely rare.

[SubPointSupport]

As IsVisible property does not work properly due to SharePoint bug, a workaround should be considered:

• Emulate IsVisible property via available means, is possible
• Delete the whole link (not a great idea, as it would loose the ordering over the next deployment)
• Consider a new definition to implement "delete" operation due to lack of "visibility" change
• Consider setting a fake audience as SharePoint group so that the link would not pop up (oh boy, just adding an idea)
• http://stackoverflow.com/questions/2624258/spnavigationnode-isvisible-property-not-working-in-sharepoint-as-expected
• http://sharepoint.stackexchange.com/questions/116259/problems-hiding-or-setting-the-audience-on-a-link-within-the-quick-launch

[SubPointSupport]

Added DeleteTopNavigationNodesDefinition / DeleteQuickLaunchNavigationNodesDefinition.
Implemented for both CSOM/SSOM, covered by the following tests:

• CanDeployRandom_DeleteTopNavigationNodesDefinition
• CanDeploy_DeleteTopNavigationNodes_ByTitle
• CanDeploy_DeleteTopNavigationNodes_ByUrl
• CanDeploy_DeleteTopNavigationNodes_ByTitleAndUrl
• CanDeployRandom_DeleteQuickLaunchNavigationNodesDefinition
• CanDeploy_DeleteQuickLaunchNavigationNodes_ByTitle
• CanDeploy_DeleteQuickLaunchNavigationNodes_ByUrl
• CanDeploy_DeleteQuickLaunchNavigationNodes_ByTitleAndUrl

[babakb]

Hi
Just wondering which version have this class "DeleteQuickLaunchNavigationNodesDefinition" ?

[SubPointSupport]

Upcoming 1.2.70
Will also include a list of all definitions per version, here is a ticket: #846

[babakb]

Cool, when do you think it will be published?

[SubPointSupport]

Over the weekend or Monday. Testing internally.

What are the scenarios you are looking for?

[babakb]

Just want to hide/remove some OOTB navigation from Quick lunch and as the rest of project is on SPMeta2 don't want to use CSOM.

[babakb]

Hi again. I've tested DeleteQuickLaunchNavigationNodesDefinition class with my scenario from your dev branch and it's working fine. I removed all OOTB navigation and added new ones. just waiting for a published version (1.2.7)

[SubPointSupport]

Thanks @babakb, appreciate your feedback.

Curious on the particular OOTB nodes in your scenarios. What are they? Would you please provide more context, so that we would add this case in the regression tests as well.

Next, we aren't sure how to get the right deleting experience for the 2nd/3rd navigation nodes. Current implementation works well for the 1st level only. Guess, will leave it as it is for the time being until the community asks for more cases.

1.2.7 is being tested, delaying. Current dev is stable for both CSOM/SSOM.

[babakb]

I'm using it for project sites on project online. they have a few default navigation (Notebook-Documents-Tasks-Calendar-Projects-Project details) which in our scenario should be removed. they are all 1st level navigation nodes.

Just as a sample :

static DeleteQuickLaunchNavigationNodesDefinition OOTBNotebook = new DeleteQuickLaunchNavigationNodesDefinition
{NavigationNodes = new List<NavigationNodeMatch>() { new NavigationNodeMatch(){Title= "Notebook",}}};

var projectWebModel = SPMeta2Model.NewWebModel(web =>
{web.AddDeleteQuickLaunchNavigationNodes(OOTBNotebook)});
var csomProvisionService = new StandardCSOMProvisionService();
csomProvisionService.DeployWebModel(projectSiteClientContext, projectWebModel);

[SubPointSupport]

Right, makes perfect sense. Thank you for sharing that.

[babakb]

Any update on publishing version 1.2.7?