Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Dim: AdminConsole: Error AUR: A user has already been assigned as primary to role DEVELOPER, design-part QLARIUS, variant A, and Project NULL
When adding a user to a role as a primary or leader capability, the following error may be received: Error AUR: A user has already been assigned as primary to role DEVELOPER, design-part QLARIUS, variant A, and Project NULL
CMS-XML Dim CM: The Copy Role option in Adminconsole generates errors where roles are assigned against projects
:TEST_PROJECT1" You can see the that product id for the /WORKSET parameter is incorrectly set to NULL rather than what it should be. Note that any role assignments that were made without a specific project are copied correctly.
CMS-XML DM2009: Error adding a primary role as both real and delegation candidate
In the adminconsole you can add a real role and a delegation candidate role to a single user. This works if you add the roles as secondary or leader. With a primary if you add the real role first you get this error while trying to add the delegation candidate role , Error AUR: A user has already been assigned as primary to role , design-part , variant NULL and Project Null If you add the delegation candidate role first and then add the real primary role second you do not get an error.
CMS-XML Dim CM 14.3: Build fails with error "COR1601014E The SCBC said (data): Internal SPI error: Error: userName is null
The message "Error: userName is null " is caused by a blank entry in the role assignments for a group and once you remove the role assignments from the groups and assign the roles required directly to the user the build runs without that error.
CMS-XML KM-Dim9: dmpmcli: Error: Cannot include system attribute PCMS_CHDOC_DETAIL_DESC in any role section
To correct this problem in dmpmcli, set the displayable attribute to false, as in the snipet below: var details = null ; var details1 =null;
CMS-XML KM-Dim9:2004-FATAL_DESIGN_APP_PAGE_NO_NULL Fatal Internal Error: Cannot hide the application page as its page number is determined to be null.
Does the problem occur on for all users? If not, is there anything consistent about the users who get the error (ie: is it only users with the developer role )?
CMS-XML KM-Dim10: CRDB SQL-1400(10085d050) ORA-01400: cannot insert NULL into
SQL-1400(0158C008) ORA-01400: cannot insert NULL into ("PAYROLL"."RM_ ROLES "." ROLE _UID")
CMS-XML KM-Dim7: How to configure Dimensions to restrict users to a specific work set.
Assign the role required to create the item to the the user, but specify a work set. Then ensure no users have the role with a null entry for the work set. Assigning roles this way will restrict the users to being able to user the role only within that specific workset.
HTML SBM Version Diff
Differences Between Versions .appendTo(this.document.find(this.options.appendTo||"body")[0]).menu({input:e(), role : null }).zIndex(this.element.zIndex()+1).hide().data("menu"),this._on(this.menu.element,
PDF Serena Dimensions Express Reports Guide
The design part variant at which the role is allocated (upper case). A null value indicates that the role is allocated for all variants of the design part.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs