Apitchaya.
I'm currently working with a client that has deployed build 0910037100. Their configuration is to start at the user's own root, but the usual configuration (as you described) is not allowing them to navigate upwards in the structure from that root; though they can search for an org unit and the navigation then works fine.
I reported the issue via OSS and SAP passed the issue on to Nakisa about a week ago. I've just checked and I've had a response. Whilst I'm pretty confident that I have done the configuration as they requested, there's always the chance I missed or mistyped something. Unfortunately I won't get chance to check now until some time on Tuesday.
I think it would be worth you reviewing your configuration against the official information they have sent me. If the issues persists then submit via OSS and include screen shots of the details they are referencing to prove that you have configured it correctly. That's what I plan to do should my configuration in fact be as per their instructions.
Info received via OSS:
Step 1: Get the Nakisa OrgChart latest build to deploy the application.
Step 2: In Admin Console set up dynamic rooting.
Go to the hierarchy wizard of an org chart's root hierarchy (for example Organizational Structure in OrgChart). Choose the following:
Orgchart root value source = User record
User record field = Organizational Unit (Org_unit)
Step 3: In SetingsResources set AllowUpLevelForRootTypeUser = true
AllowUpLevelForRootTypeUser.txt should be a text file and not an xml file.
The content of the text file should just be one word: 'true' (without the quotation marks)
Note: If the setting AllowUpLevelForRootTypeUser does not exist in SettingsResources, it is the same as AllowUpLevelForRootTypeUser = false
Step 4: Publish the build.
Step 5: In the User Console verify that the button with the tooltip 'Start chart one level above' starts appearing on the root org chart box
Regards,
Stephen.