TM1 User Groups - Error Registering Object

[mystrJeff]

Hello all,

TM1 Version: 10.2

Issue: A group of users is assigned a specified User Group (ex. Group A) with limited access to cubes and processes. Obviously with an ADMIN role, a user can run any TI process without any issues. However, once logged into this specific group, the message "Error Registering Object" dialog box appears. Here's the kicker which I'm hoping someone can shed a light on - If I log in as one of the users in Group A on my physical desktop machine, I am able to run the process with no issues. However on other machines, they receive the "Error Registering Object" message.

Has anyone ever experienced this before? Is there a file that might need registering?

Thanks in advance for any help!

[Alan Kirk]

Issue: A group of users is assigned a specified User Group (ex. Group A) with limited access to cubes and processes. Obviously with an ADMIN role, a user can run any TI process without any issues. However, once logged into this specific group, the message "Error Registering Object" dialog box appears. Here's the kicker which I'm hoping someone can shed a light on - If I log in as one of the users in Group A on my physical desktop machine, I am able to run the process with no issues. However on other machines, they receive the "Error Registering Object" message.

The obvious question is "what is the exact code that is generating this error"?

Also, on the off chance that it has something to do with updating a security object (which we have no way of knowing at this point), is the Security Access option checked on the process?

In reality I suspect that it's more likely to be an issue with trying to recreate an existing object, but again we can do nothing more than guess at this point.

[mystrJeff]

Hello, thanks for replying.

Indeed the process is using a view that gets recreated when it is run.
In the prolog tab, I have a subprocess running that updates a view, and in the data tab:

Code: Select all

   scno_cd = DimensionElementPrincipalName( app_cd |'_scno', vScno );
  emp_cd = DimensionElementPrincipalName( 'emp', vEmp );
  mtr_cd = DimensionElementPrincipalName( src_mtr_dn, vMtr );

  IF( DTYPE( tgt_msr_dn, mtr_cd ) @='S');
    IF( CellIsUpdateable( tgt_cn, scno_cd, emp_cd, mtr_cd )>0 );
      CellPutS(
        CellGetS( src_cn, scno_cd, emp_cd, mtr_cd, 'src' )
      , tgt_cn, scno_cd, emp_cd, mtr_cd
      );
    ENDIF;
  ELSE;
    IF( CellIsUpdateable( tgt_cn, scno_cd, emp_cd, mtr_cd )>0 );
      CellPutN(
        StringToNumber(CellGetS( src_cn, scno_cd, emp_cd, mtr_cd, 'src' ))
      , tgt_cn, scno_cd, emp_cd, mtr_cd
      );
    ENDIF;
  ENDIF;

The premise of the process is to pull any data changes through into the calculations. If something had changed within a data import, I have a "difference" cube to catch all changes. This process will allow the changes to be "active".

The view that is being changed is: anywhere in the source cube where a change occurs, put that employee into the view.


And to answer your other question: the Security Access option is checked on the process.

---

Just seems strange to me that same code and same users on different machines would yield different results. One allowing the process to be run, the other throwing the "Error Registering Object" popup.

Thank you for your time.