Change th

[dwhcognos8]

Hi All,
Can i change the CAMID("AD:u:42eb7282-863811dd-80ebd174-abcb477b") created by CognosBI/AD to the Original Id(Employee Id) mentioned in Active Directory?

I mean if i had Employee Id as unique, created for each and every user which is decoded into CAMID("AD:u:42eb7282-863811dd-80ebd174-abcb477b") by CognosBI/AD, Can i get Employee Id instead the Decoded CAMID("AD:u:42eb7282-863811dd-80ebd174-abcb477b") into TM1???
Do we have any setting to be done on the Cognos Configuration Side? Pls let me know!

Thanks, Sri

[sachin]

In TM1 you can use the alias to get the actual employee id. The attribute name you need to look for is }TM1_DefaultDisplayValue

[dwhcognos8]

Thanks Sachin for the reply,I am aware that we can use the alias }TM1_DefaultDisplayValue in }Client Dim in TM1 but i want to manage the CAMID parameter when passing from Cognos BI to TM1.
Is there any option to send the original Emp id instead the CAM ID from Cognos BI to TM1?

Regards, Sri

[dwhcognos8]

I guess nobody had encountered this scenario till Now i guess!

[lotsaram]

I guess nobody had encountered this scenario till Now i guess!

I wouldn't say no one has encountered it, just a fact of life that the CAM ID string is ugly as all hell.

[normanbobo]

Lotsaram and others ....

I'm currently dealing with the issue of CAMID's and Contributor at a client.

One thing I have noticed is that if you add the user id's manually (inside TM1 security, add the client manually), the "display" version appears accurately. However, if the user id does not exist when the user first logs in, the CAMID appears. Personally, I think this is a bug.

As most of you probably know, the lack of a display name causes problems with contributor, namely creating directories in the sandboxlogs directory on the server (because the CAMID's contain a colon, which is an invalid character for directory names).

I'm not excited about it, but a workaround I plan to test is, when you add the user to the Cognos groups (a step you have to do either in Cognos or in your namespace at some point to give the user access), also perform the manual step to add the user to TM1 security manually.

But I would definitely be interested in anyone's thoughts on this, especially if anyone has found an automated way to set the display value when a user logs in without the client already having been defined in TM1 security.

[normanbobo]

One thing I have noticed is that if you add the user id's manually (inside TM1 security, add the client manually), the "display" version appears accurately. However, if the user id does not exist when the user first logs in, the CAMID appears. Personally, I think this is a bug.

IBM has since confirmed that this is a bug. It has been addressed in 10.1.0 but will not be addressed in 9.5.2. (Yet another example of why it is important to keep your Cognos software updated).

I'm not excited about it, but a workaround I plan to test is, when you add the user to the Cognos groups (a step you have to do either in Cognos or in your namespace at some point to give the user access), also perform the manual step to add the user to TM1 security manually.

This is the only workaround. Ugly and inefficient, but works.

But I would definitely be interested in anyone's thoughts on this, especially if anyone has found an automated way to set the display value when a user logs in without the client already having been defined in TM1 security.

Anyone have any ideas?

[lotsaram]

Rather than creating users manually in TM1 after they are created in Cognos but before the user gets a chance to log on to TM1 why not have a regularly scheduled overnight job to write out users and group memberships either to a file or RDBMS then delete all the users then have another job to recreate the users and assign them to groups. Then surely from TM1's perspective the users must be as if they were created manually but no extra manual work needs to be done.

I would have thought worth a shot or have you tried this already?