Contributor Work Flow Dimension Add

[cdhodge2002]

I am having and issue when new projects showing up in my work flow dimension hierarchy.

Basically on a regular basis new project will start in my application and once the project are approved data is moved from a project entry cube to an active product cube. The active product cube has a work flow dimension that has projects by location. However when my projects are added to the workflow dimension you are not able to see them in the contributor app. Currently my subset is a dynamic subset using the following code:

{TM1DRILLDOWNMEMBER( {TM1SubsetBasis()}, ALL, RECURSIVE )}

Is there a way to get these new items to show up in the work flow hierarchy automatically?

[tomok]

{TM1DRILLDOWNMEMBER( {TM1SubsetBasis()}, ALL, RECURSIVE )}

Change your MDX code to:
{TM1DRILLDOWNMEMBER( {TM1SubsetAll()}, ALL, RECURSIVE )}

[moby91]

Maybe you reconsider to use TM1DrilldownMember in the MDX expression to calculate the dynamic subset you are using as approval hierarchy, see the IBM Technote 1568864:


https://www-304.ibm.com/support/docview ... wg21568864
TM1 Contributor - Workflow page is blank

Technote (troubleshooting)

Problem(Abstract)
Non-Admin user is not able to see it's secured nodes on the workflow page.
New application or newly modified

Symptom
User (non-Admin) logs into Tm1 Contributor, selects the Tm1 Contributor application and the workflow page loads on the browser, but it is blank. None of the node secured for this user are listed.

Cause
Approval Hierarchy Dimension Subset is dynamic. It is not possible to use an MDX with TM1DrilldownMember


Resolving the problem

1- Remove the expression (MDX) from the subset and save
or
2- Modify the MDX and not use TM1DrilldownMember


Example:
TM1DrilldownMember([dimension].[item], ALL, RECURSIVE)

Instead use an expression of the form:
FILTER([dimension].members, ISANCESTOR([region].[item],[dimension].currentmember)

[cdhodge2002]

I have seen that technote but it is super cryptic as to what I need to write.

FILTER([dimension].members, ISANCESTOR([region].[item],[dimension].currentmember)

I am not sure what the region section is supposed to specify.

Dimension should be the dimension name

Item is the Total level item I want for the hierarchy.

Any help on this?

[PlanningDev]

I concur with the suggestions listed.

We ran into this issue using dyanamic subsets for approval hierarchies. One issue is that for each item in the approval hierarchy subset, a specific contributor group must be created. This group is not created when adding items to the dimension. It is only created when doing specific tasks within contributor administration. You may be able to solve some of this by running one of the contributor control TIs to create groups.

In one case our dynamic subset for approval hierarchy would not even let the end users open a node.

It may be best to avoid using the dynamic subset and go the route of using a TI to add the new projects to the subset and then force a create groups through the backend TI.