- changed status to on hold
Adding private apps to favorites and selecting as homepage
Homepage: This picklist in the homepage dropdown is only considering public dashboards. The picklist needs to be adjusted to filter dashboards from Public apps + my apps.
Favorites: When you try to add a private app to favorites, it does not add and does not give any errors.
Comments (9)
-
-
It appears that if we modify the “Picklist - Homepage Selection” dynamic subset in the “}APQ UX App” dimension, we can achieve the ability to show private pages. I tried appending “{Generate({StrToSet("{[}APQ UX App].["+USERNAME+"].Children}")},{[}APQ UX App].CurrentMember.Children})}” to the existing dynamic subset and it seems to show the private pages for each user.
-
My proposed MDX needs to be edited to consider private pages that are nested in UX private folders (updated MDX below). Also, for this to work with CAM authentication, we need an additional alias on “}APQ UX App” that stores the CAMID principal name (e.g., CAMID(“…”)). When a private app is created and the new element (corresponding to the user name) is added, the value of this attribute needs to be set. Otherwise USERNAME in the MDX would not work since the new element added is based on the “}TM1_DefaultDisplayValue” alias.
{{{StrToSet("{Filter({Descendants({[}APQ UX App].["+USERNAME+"]})},[}APQ UX App].[AppType]='View')}")},{StrToSet("{Filter({Descendants({[}APQ UX App].["+USERNAME+"]})},[}APQ UX App].[AppType]='Dashboard')}")},{StrToSet("{Filter({Descendants({[}APQ UX App].["+USERNAME+"]})},[}APQ UX App].[AppType]='Wizard')}")}}}+{{ORDER({FILTER( {DESCENDANTS( [}APQ UX App].[}APQ UX App].[Main], 1, SELF_AND_AFTER )}, ( [}APQ UX App].[}APQ UX App].CurrentMember.Properties("AppType") = "Dashboard" AND [}ElementAttributes_}APQ UX App].([}APQ UX App].[}APQ UX App].CurrentMember,[}ElementAttributes_}APQ UX App].[WizNo]) = 0 ) )}, [}APQ UX App].[Position], ASC )}+{ORDER({FILTER( {DESCENDANTS( [}APQ UX App].[}APQ UX App].[Admin], 1, SELF_AND_AFTER )}, ( [}APQ UX App].[}APQ UX App].CurrentMember.Properties("AppType") = "Dashboard" AND [}ElementAttributes_}APQ UX App].([}APQ UX App].[}APQ UX App].CurrentMember,[}ElementAttributes_}APQ UX App].[WizNo]) = 0 ) )}, [}APQ UX App].[Position], ASC )}}}
-
@Wei Wang To include private apps in homepage selection the MDX can be much simpler with no need for generate as private apps can be filtered by the user attribute which uses principal name of }Clients so can just use USERNAME in MDX.
e.g.
sMDX = '{{FILTER({{ORDER({FILTER({DESCENDANTS([}APQ UX App].[}APQ UX App].[Private], 1, SELF_AND_AFTER)}, (([}APQ UX App].[}APQ UX App].CurrentMember.Properties("AppType") = "Dashboard" OR [}APQ UX App].[}APQ UX App].CurrentMember.Properties("AppType") = "View") AND [}ElementAttributes_}APQ UX App].([}APQ UX App].[}APQ UX App].CurrentMember,[}ElementAttributes_}APQ UX App].[WizNo]) = 0))}, [}APQ UX App].[Position], ASC)}+{ORDER({FILTER({DESCENDANTS([}APQ UX App].[}APQ UX App].[Private], 1, SELF_AND_AFTER)}, [}APQ UX App].[}APQ UX App].CurrentMember.Properties("AppType") = "Wizard")}, [}APQ UX App].[Position], ASC)}}, [}APQ UX App].[}APQ UX App].CurrentMember.Properties("User") = USERNAME)}+{{ORDER({FILTER({DESCENDANTS([}APQ UX App].[}APQ UX App].[Public], 1, SELF_AND_AFTER)}, (([}APQ UX App].[}APQ UX App].CurrentMember.Properties("AppType") = "Dashboard" OR [}APQ UX App].[}APQ UX App].CurrentMember.Properties("AppType") = "View") AND [}ElementAttributes_}APQ UX App].([}APQ UX App].[}APQ UX App].CurrentMember,[}ElementAttributes_}APQ UX App].[WizNo]) = 0))}, [}APQ UX App].[Position], ASC)}+{ORDER({FILTER({DESCENDANTS([}APQ UX App].[}APQ UX App].[Public], 1, SELF_AND_AFTER)}, [}APQ UX App].[}APQ UX App].CurrentMember.Properties("AppType") = "Wizard")}, [}APQ UX App].[Position], ASC)}}}';
This is the fix we will put into the next 2021.11 FP
-
As for favorites, private screens are being flagged correctly as favorites. It is just the MDX we are running to retrieve current favorites only looks at public views. Should be an easy fix.
-
- changed status to open
-
This will be addressed in a fixpack to 2022.06 release
-
- changed status to resolved
resolved and will be part of June FP1 release
-
- removed milestone
Removing milestone: 2022_Q2 (automated comment)
- Log in to comment
Has been added to our issues backlog