Nivel 1
Nivel 2
Iniciar sesión en la comunidad
Iniciar sesión para ver todas las insignias
We currently use a project report that users can see a list of open project on which they're a team member. A few users have asked if the report can be revised to only show projects on which they still have open tasks. They rather not see projects in their list if all if their tasks are completed, even if the project is still open for others to work on.
I prefer not to use a task report in this instance- just need project info, not a list of tasks.
I know there are (severe) limitations on crossing project and task information in reports, but wondering if anyone has been able to solve for something like this?
Thanks!
¡Resuelto! Ir a solución.
Los temas ayudan a categorizar el contenido de la comunidad e incrementan la posibilidad de encontrar contenido relevante.
Vistas
Respuestas
Total de me gusta
Hi - this was a fun challenge to end my week! I think I got it figured out for you using an EXIST filter. Hope it helps you.
EXISTS:1:$$OBJCODE=ASSGN
EXISTS:1:projectID=FIELD:ID
EXISTS:1:assignedToID=$$USER.ID
EXISTS:1:assignedToID_Mod=in
EXISTS:1:task:status=CPL
EXISTS:1:task:status_Mod=notin
EXIST filters let you jump an object type (so in this case I wanted to do Assignment filters on a Project report (skipping the task hierarchy). It is also great when you are moving down the hierarchy instead of up.
Here is my little cheat sheet when you want to move down the hierarchy. Hopefully it makes sense. It relies on the API Explorer (https://one.workfront.com/s/api-explorer)
Moving Down The Hierarchy
This is for reports where you want to apply a filter based on a many-to-one relationship (Like portfolios that have projects Anthony owns)
EXISTS:1:$$OBJCODE=[Insert Object Code for the Collection]
EXISTS:1:[Collection Object Type's field that matches current object]=FIELD:[Current Object Type's field that matches collection object]
EXISTS:1:[Field on Collection being filtered]=[Condition]
Based on my Example:
EXISTS:1:$$OBJCODE=PROJ
EXISTS:1:portfolioID=FIELD:ID
EXISTS:1:ownerID=532376910024d8443277c3e46ed5330a
EXISTS:1:ownerID_Mod=in
Vistas
Respuestas
Total de me gusta
Hi - this was a fun challenge to end my week! I think I got it figured out for you using an EXIST filter. Hope it helps you.
EXISTS:1:$$OBJCODE=ASSGN
EXISTS:1:projectID=FIELD:ID
EXISTS:1:assignedToID=$$USER.ID
EXISTS:1:assignedToID_Mod=in
EXISTS:1:task:status=CPL
EXISTS:1:task:status_Mod=notin
EXIST filters let you jump an object type (so in this case I wanted to do Assignment filters on a Project report (skipping the task hierarchy). It is also great when you are moving down the hierarchy instead of up.
Here is my little cheat sheet when you want to move down the hierarchy. Hopefully it makes sense. It relies on the API Explorer (https://one.workfront.com/s/api-explorer)
Moving Down The Hierarchy
This is for reports where you want to apply a filter based on a many-to-one relationship (Like portfolios that have projects Anthony owns)
EXISTS:1:$$OBJCODE=[Insert Object Code for the Collection]
EXISTS:1:[Collection Object Type's field that matches current object]=FIELD:[Current Object Type's field that matches collection object]
EXISTS:1:[Field on Collection being filtered]=[Condition]
Based on my Example:
EXISTS:1:$$OBJCODE=PROJ
EXISTS:1:portfolioID=FIELD:ID
EXISTS:1:ownerID=532376910024d8443277c3e46ed5330a
EXISTS:1:ownerID_Mod=in
Vistas
Respuestas
Total de me gusta
Thank you so much, this was really helpful. I also added an EXISTS:1 for 'project status equates with' to just show those that are 'open'. So far it seems to be what I needed. Thank you!
Vistas
Respuestas
Total de me gusta
Vistas
me gusta
Respuestas
Vistas
me gusta
Respuestas
Vistas
me gusta
Respuestas