Hello All,
We are facing a strange issue while using contributor (TM1 9.5.2)
We have configured a flag in view, setting a Y value for flag will make all measures a read only for that specific record and for N, all with write access(editable). This works fine in TM1 Web and Architect, but now sure why not in Contributor.
Any suggestion , please let me know.
Thanks,
Manoj
Update issue in View through Contributor
- jim wood
- Site Admin
- Posts: 3961
- Joined: Wed May 14, 2008 1:51 pm
- OLAP Product: TM1
- Version: PA 2.0.7
- Excel Version: Office 365
- Location: 37 East 18th Street New York
- Contact:
Re: Update issue in View through Contributor
How are you making the measures read only / write? Are you using rules for security? We really need more detail from you before we can come close to helping you.
Struggling through the quagmire of life to reach the other side of who knows where.
Go Build a PC
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7
Go Build a PC
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7
-
- Posts: 60
- Joined: Thu Mar 17, 2011 2:13 pm
- OLAP Product: IBM Cognos TM1
- Version: 10.2.1
- Excel Version: 2010
Re: Update issue in View through Contributor
Actually, we created a cell Security cube for our main cube and there using rules, we have defined rule as :
['user group', {'Set of fields}] = S:IF(DB(Main Cube,.........,......, 'Flag') = 'Y' , Read, Write).
It works fine when you make any change in flag value using TM1 web or thru Architect. But using Contributor on same view, it just works for first time and for one record, not for any another record even after committing data. Not sure why.
Please let me know if you need any further info.
Thanks,
Manoj
['user group', {'Set of fields}] = S:IF(DB(Main Cube,.........,......, 'Flag') = 'Y' , Read, Write).
It works fine when you make any change in flag value using TM1 web or thru Architect. But using Contributor on same view, it just works for first time and for one record, not for any another record even after committing data. Not sure why.
Please let me know if you need any further info.
Thanks,
Manoj
- jim wood
- Site Admin
- Posts: 3961
- Joined: Wed May 14, 2008 1:51 pm
- OLAP Product: TM1
- Version: PA 2.0.7
- Excel Version: Office 365
- Location: 37 East 18th Street New York
- Contact:
Re: Update issue in View through Contributor
Security done by rules only works when you do a security refresh. You may be getting lucky within Architect dur to cached values. Have you tried doing it straight after a server restart? My guess is that contributor is not using the cached values when TM1 web and architect are.
Struggling through the quagmire of life to reach the other side of who knows where.
Go Build a PC
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7
Go Build a PC
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7
- jim wood
- Site Admin
- Posts: 3961
- Joined: Wed May 14, 2008 1:51 pm
- OLAP Product: TM1
- Version: PA 2.0.7
- Excel Version: Office 365
- Location: 37 East 18th Street New York
- Contact:
Re: Update issue in View through Contributor
If you search you'll find plenty of information on the forum regarding security and rules. I myself built a workflow security model only 6 months ago. Originally it was in rules but I moved to TI after hitting the issue I mentioned above. If you search my posts you'll find it soon enough.
Struggling through the quagmire of life to reach the other side of who knows where.
Go Build a PC
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7
Go Build a PC
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7
-
- MVP
- Posts: 2836
- Joined: Tue Feb 16, 2010 2:39 pm
- OLAP Product: TM1, Palo
- Version: Beginning of time thru 10.2
- Excel Version: 2003-2007-2010-2013
- Location: Atlanta, GA
- Contact:
Re: Update issue in View through Contributor
That is true except for one exception. cell level security, which is what the OP has used. Cell level security is not cached, which is one of the reasons it is so slow. I never use it unless absolutely forced to.jim wood wrote:Security done by rules only works when you do a security refresh.