In Splunk Cloud, how do I reassign knowledge objects when they don't show up in "Reassign Knowledge Objects"?

[BlueSocket]

Dear All,

I am running on Splunk Cloud 9.0.2208.3 as a sc_admin-rolled user and I have created a load of calculated fields as my user for the administrators to see data in the associated Data Models. I have made the Calculated Fields non-private - i.e. in the app/global as appropriate.

All is good and others can see the data in the DMs, however, I am leaving the company and they are going to have to delete my user as a part of the offboarding process (plus I don't want to be blamed if someone hacks the system and it was my user, somehow).

As a result, I want to reassign my KBOs to the nobody user, so that my user is no longer in the circuit and can be safely deleted, however, when I go into "Reassign Knowledge Objects", I cannot see the Calculated Fields at all. I have made sure that I can see KBOs in all apps and all users and still no dice.

Why can't I reassign these KBOs??? How can I do this? Or perhaps, do I NEED to do this?

[richgalloway · Accepted solution]

Yes, the KOs need to be reassigned to avoid becoming orphaned.  You'll need to submit a support request for that.  The request should name every KO to be reassigned as well as the new owner.  Consider creating a service account to be the new owner to avoid this problem in the future.

[BlueSocket]

Thanks for your response, @richgalloway . I will do so.