cancel
Showing results for 
Search instead for 
Did you mean: 

Dynamic rooting is not working for majority of the users ids

Former Member
0 Kudos

Dear All

Dynamic rooting is correctly working for only few user ids but is not working for most of the user ids. We are getting an error message - "Cannot find the root of your orgchart. The orgchart box may have been deleted or incorrectly specified, or no valid org structure can be found for the selected effective date. Please change the root of the chart or select another effective date".

  • The issue is not related to authorization as we have assigned the correct roles & have even tested with SAP_ALL profile. But the issue still persists.
  • We are testing for one of the standard hierarchy of Nakisa.
  • All active employees are assigned to an valid Org unit
  • We are using the live connection
  • OrgChart General settings made --- Orgchart root value source = User record , = Org Unit ID (Org_Unit)
  • By assigning the static root Org unit the hierarchy view is working fine for all the user ids.
  • Even if we set the root org unit to the one to which our test account id (which is given an error) is assigned then also We can correctly see the occupied position in the chart that corresponds to the employee for whom  the user account is assigned.
  • We have created few custom Nakisa roles in portal & have also role mapped it with custom Nakisa backend roles (which were copies of the standard roles as listed below)

        

RoleStd roles copied
Manager Nakisa - Line Manager
EmployeeNakisa - Executive
EveryoneNakisa - Role for Everyone

Note:- If we test the same scenarios using the standard Live_RFC build, all the scenarios for all the user ids are working fine. Also in the standard build copy we did not do any role mapping. But still single sign-on configuration is working.

The issue is coming for our custom build only.

The Warning messages we are getting in the log are:

        WARN com.nakisa.Logger - Configuration merge warning: : Right configuration is null - Merge skipped!

        WARN com.nakisa.Logger - ChartingProcessor : renderChart : Empty Struct passed to render chart for rendering

The sample Data we are using is :

Roleuser idsPERNREmp NameOrg UnitPosition DescriptionDynamic rooting Result
ManagerID_01500001Emp 1CEO & President OfficeCEOWorking Fine
ID_0247Emp 2DIR.QUALITY ASSURANCESVP | QUALITY ASSURANCENOT Working
Employee (executive)ID_03500003Emp 3DIR.QUALITY ASSURANCEQuality OfficerNOT Working
Everyone (supervisor)ID_0450Emp 4EXC.VICE PRESIDENCY, (HUMAN RESOURCES)CHRO (CHIEF HUMAN RESOURCES OFFICER)Working Fine
HRID_0551Emp 5DIR. PERSONNELSVP | PERSONNELNOT Working

Kindly guide us in resolving the issue.

Regards

Ravindra

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Ravindra,

Just to add to Luke's answer.

Check out this KBA which are some questions we ask customers dealing with this error.

1708773 - Cannot find the root of your OrgChart

Kind Regards,

Matthew

Former Member
0 Kudos

Dear All

We were able to resolve this issue. It was mainly an data issue.

We had activated another language along with the English language & had set the other language as the default language. For our test data Org units, data was not maintained in the other language.

Once when we maintained the Org unit data in the other language (which was the default language in Nakisa) using PP02 transaction & tested the dynamic rooting was working correctly for all the different test scenarios.

Really we learned the hard way!

Regards

Ravindra

Answers (1)

Answers (1)

lukemarson
Active Contributor
0 Kudos

Hi Ravindra,

Usually Nakisa would provide the same error for all users, rather than for some and not for others. Initially I would begin my investigation on the backend.

As per the forum rules, please provide the application version and cds.log for the working and not working logins.

I suggest you check the authorizatons of your role mapping user as this is what retrieves the user object. It might be that it cannot retrieve the org data for some orgunits and therefore the user object doesn't contain the orgunit ID.

Best regards,

Luke