cancel
Showing results for 
Search instead for 
Did you mean: 

Adding a custom SAP field as searchable field in Nakisa search

PT3
Participant
0 Kudos

We have a custom field on Infotype 0001, which based on a business rule, stores the Position ID of the Executive VP of an employee. We want to use this custom field as a search criteria within the 9-box grid.

We want to know how this field can be added in Nakisa and be available as a part of the search fields. We have tried adding it as a part of the XML, but it did not work.

Thanks,

Prashanth

Accepted Solutions (0)

Answers (2)

Answers (2)

StephenMillard
Active Contributor
0 Kudos

Hi Prashanth.

Can you provide an update on how you got on with this?

Regards,

Stephen.

StephenMillard
Active Contributor
0 Kudos

Hi Prashanth.

Which XML files have you made amendments to and what have those amendments been?

Regards,

Stephen.

PT3
Participant
0 Kudos

Hi Stephen,


We updated SAPEmployeenineboxsearch.xml; added YYEXECUTIVE field under table EmpPersonalDataPA0001. Also, we added Manager field variable in output tables SAPEmployeeNineBoxSearch/SAPEmployeeNineBoxSearchTemp in the XML. 

The doubt we is whether just updating new XML in OTF structure enough to see change in Nakisa? We updated one XML for Risk of Loss and one for Manager search, but couldn’t see ANY change in Nakisa Talent hub. Not sure if we need to change any pointers at other places as well OR if we are updating XML’s in the right directory in the first place?


Thanks,

Prashanth

StephenMillard
Active Contributor
0 Kudos

Okay - first thing's first.  Let's verify that you are editing files in the right place.

If you navigate to your installation, you should be able to find a .delta folder within your build folder.

...\<Nakisa Application>\root\.system\Admin_Config\__000__<build name>\.delta\

Within the folder structure inside of the .delta folder is where you should make any file amendments.

Once the amendments are done you load the build into AdminConsole and publish it.  Then close your browsers, reopen and login to test.

Don't forget to backup your build configuration (option within AdminConsole) or at least the files you are modifying prior to making build changes.

Does the above approach match to what you've been doing in terms of file level updates?

Regards,

Stephen.

PT3
Participant
0 Kudos

Hi Stephen,

We’ve added XML’s to \__000__<buildname>\.delta\OTFSchema\functionConfiguration folder and published the updated load, but we still don't see any change in the Talent Hub.

Thanks,

Prashanth

StephenMillard
Active Contributor
0 Kudos

Prashanth.

Amending the functionConfiguration will bring data in from the SAP system to the Nakisa application.  You then need to map that all the way through to where you want to present it.

I'd perhaps start by taking a look at ...\AppResources\dataelementconfiguration\SAPEmployeeSearch_With_NineBox.xml

That's probably where your initial mapping wants to take place (you mentioned search in the initial posting).  From there you'll need to work your way through the detaildataconfiguration and detailconfiguration files as a minimum I would have thought.

I've not modified the nine box myself but there's also a ...\AppResources\gridconfiguration\GridConfiguration_ninebox.xml file that looks like it might be worth a closer look.

There are also likely to be other files you might need to amend around presentation (XSL, etc.)

Nakisa applications behind the scenes are built on hierarchies of XML files.  Hopefully you're comfortable working around and figuring out the hierarchy to apply this sort of change.  If not, have you tried checking in AdminConsole to see if that will let you add in your additional field?

Regards,

Stephen.