Filters created in a folder link are not visible after page refresh
search cancel

Filters created in a folder link are not visible after page refresh


Article ID: 161800


Updated On:


IT Management Suite


If you create a filter in a folder link, the filter will be created, and show up, but if you refresh the page it will not be there anymore.

Steps to reproduce:

1. Settings -> All Settings -> Notification Server -> Console Settings -> Views -> Create a new view

2. On the Edit View page -> Tree drop-down -> select Resources

3. Add the "Filters" folder (or any other folder inside) to the view contents and click OK to save the view

4. Settings -> All Settings -> Notification Server -> Console Settings -> Menus

5. Add a new menu -> in the show option select view and then specify the view created in the step 3 -> Save changes

6. Click on the top menu created in previous step to open up the view

7. In the view, right click on the "Filters" folder (shortcut) and create a new filter. You should see it in the tree until you refresh the page.

Right after you create a new filter, you should see the following warning in the logs:

Error moving Item guid 5deb0546-dd54-4b46-8eeb-795e016356d9 to folder guid 64604304-5982-41b3-a9ec-c4b9fe5d2d00. Folder does not exist.
   at Altiris.NS.ItemManagement.Item.MoveToFolder(Guid folderGuid, Boolean checkSecurity)
   at Altiris.NS.ItemManagement.Item.MoveToFolder(Guid folderGuid)
   at Altiris.NS.ItemManagement.Folder.MoveToFolder(Guid childItemGuid, Guid folderGuid)
   at Altiris.NS.UI.Admin.Collections.frmNewNSResourceCollection.Page_Load(Object sender, EventArgs e)
   at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
   at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
   at System.Web.UI.Control.OnLoad(EventArgs e)
   at Altiris.NS.UI.Controls.PageCachePage.OnLoad(EventArgs e)
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
   at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
   at System.Web.UI.Page.ProcessRequest()
   at System.Web.UI.Page.ProcessRequest(HttpContext context)
   at Altiris.NS.UI.Controls.PageCachePage.ProcessRequest(HttpContext context)
   at Altiris.NS.UI.AltirisPage.ProcessRequest(HttpContext context)
   at ASP.admin_collections_frmnewnsresourcecollection_aspx.ProcessRequest(HttpContext context)
   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
   at System.Web.HttpApplication.ApplicationStepManager.ResumeSteps(Exception error)
   at System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData)
   at System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)
   at System.Web.HttpRuntime.ProcessRequestNoDemand(HttpWorkerRequest wr)
   at System.Web.Hosting.ISAPIRuntime.ProcessRequest(IntPtr ecb, Int32 iWRType)

8. Refresh the page, now you shouldn't see the filter created in previous step. The issue is reproducible only if you create a filter in the root folder (shortcut).


This issue is already fixed in 7.6 HF1. As a workaround, in the product versions prior to 7.6 HF1 you can use the options below:

Workaround 1: If it's required to create filters in a custom view, filters can be created either inside existing sub folders or a new sub folder can be created in the root folder (shortcut).

Workaround 2: Filters can be created in "Manage -> Filters" and there shouldn't be any issue to see them in a custom view.



Applies To

ITMS 7.5 SP1