cancel
Showing results for 
Search instead for 
Did you mean: 

Nakisa OrgModeler 4.1 SP1 - General information data issue & Sharing functionality issue

Former Member
0 Kudos

Hi All


With reference to the below screenshots, some of the standard functionalities are not working in Nakisa OrgModeler 4.1 SP1:

  1. General Information in the details panel is not displaying any data
  2. Share tab has no details on users & roles
  3. On viewing any orgunit / position its cost centre details are not getting displayed either in the chart or in the details view. Even in the cost centre org view also the issue exists
  4. Orgunit ID configured & displayed as Organisaton chart root in OrgModeler is different compared to the orgunit id displayed in "Create Scenario --> Choose Root"

Note:

We upgraded from Nakisa OrgChart from 4.0 SP1 to 4.1 SP1.

We had exported our custom builds before the upgrade. We are using the same custom builds after the upgrade by using the import functionality.

After the import there were no configuration changes were made to the custom build. All these functionalities were working previously

Kindly help in resolving the issue. If it is an product issue then kindly suggest so that we can raise an support message.

Regards

Ravi

Accepted Solutions (1)

Accepted Solutions (1)

StephenBurr
Active Contributor
0 Kudos

Often there are configuration changes made between product versions which means you can't simply apply your old custom build to a new version. 

See explanation here on why conflicts occur:

Have you tested the out of the box configuration (OOTB) for OM 4.1 SP1 to see if this a product issue or an issue with applying your previous configuration build?

If you can prove it is a product issue with the OOTB configuration, then you would raise a support message under application area XX-PART-NKS-VSN.

Stephen

Former Member
0 Kudos

Thanks Stephen.

We tested with the standard build & all the standard functionalities are working fine.

Hence, we are raising this defect as a support message.

Regards

Ravi

StephenBurr
Active Contributor
0 Kudos

If the OOTB works then this is not a product defect and should not be raised on SMP.

Your applied configuration is causing the issue. Either re-apply your configuration (i.e. re-do it) on the new OOTB build or you will need to analyse what the issue is by comparing the builds as per my blog post.

The company I work for spent some time investing in this area to ensure we could greatly speed up this process as there are literally 100's (if not >1000) files that need comparing to upgrade safely with confidence.

Stephen

Answers (0)