Planning Analytics

We are using PAW Local 2.94.  I have set up the Environments feature in Administration for two environments DEV and PROD.  Each environment points to a different server where there are separate TM1 instances on each.  I find that after setting up people in the security area for each environment, these individuals can not see the second when they use the dropdown next to their name.  They see the description for the first environment (DEV) but when they click the dropdown, the second isn't there.  This behavior occurs even if the individual has been set up as an Environment Administrator.

Is there some limitation with regards to using separate servers to hold the TM1 instances?  I have another installation where all the TM1 instances are on the same box and there has been no limitation to adding users to environments and users accessing.

Dean

Hi Dean,

Glad to hear you are testing out mulitenacy in Planning Analytics Workspace local.  

Assuming the user is in both environments, or they have the Environment Admin privlidge, they should see both environments in the drop down.  It shouldn't matter how the TM1 databases are distributed.  Mutli-tenancy in Workspace should work even if there are no TM1 databsaes running in the environment.  I'm assuming at least one user can see the other environment.  Does your environment admin user see the Environments tile in the Administration area of Workspace? 

Can you double check or share your paw.env/paw.ps1 file?  Are you completly sure multitenancy is enabled in the config file?

We are using PAW Local 2.94.  I have set up the Environments feature in Administration for two environments DEV and PROD.  Each environment points to a different server where there are separate TM1 instances on each.  I find that after setting up people in the security area for each environment, these individuals can not see the second when they use the dropdown next to their name.  They see the description for the first environment (DEV) but when they click the dropdown, the second isn't there.  This behavior occurs even if the individual has been set up as an Environment Administrator.

Is there some limitation with regards to using separate servers to hold the TM1 instances?  I have another installation where all the TM1 instances are on the same box and there has been no limitation to adding users to environments and users accessing.

Dean

Thank you Stuart,

I can confirm that the MULTI_ENVIRONMENT flag in the paw.env file is set to 'True'.

I also found the following:

 - I gave environmental admin rights to four people.  Only two of the four can see the Environments tile and only the two that can see the tile, can see the two environments in the dropdown.

 - Everyone has access to the TM1 databases on both of the VMs.

Dean

Hi Dean,

Glad to hear you are testing out mulitenacy in Planning Analytics Workspace local.  

Assuming the user is in both environments, or they have the Environment Admin privlidge, they should see both environments in the drop down.  It shouldn't matter how the TM1 databases are distributed.  Mutli-tenancy in Workspace should work even if there are no TM1 databsaes running in the environment.  I'm assuming at least one user can see the other environment.  Does your environment admin user see the Environments tile in the Administration area of Workspace? 

Can you double check or share your paw.env/paw.ps1 file?  Are you completly sure multitenancy is enabled in the config file?

We are using PAW Local 2.94.  I have set up the Environments feature in Administration for two environments DEV and PROD.  Each environment points to a different server where there are separate TM1 instances on each.  I find that after setting up people in the security area for each environment, these individuals can not see the second when they use the dropdown next to their name.  They see the description for the first environment (DEV) but when they click the dropdown, the second isn't there.  This behavior occurs even if the individual has been set up as an Environment Administrator.

Is there some limitation with regards to using separate servers to hold the TM1 instances?  I have another installation where all the TM1 instances are on the same box and there has been no limitation to adding users to environments and users accessing.

Dean