Cannot create a runbook due to knowledge table yeilding no results.

[JulienRouge1549]

I've been moving work between instances and I've ran into an issue with runbooks and knowledge articles. The knowledge articles would port over empty and same with the runbooks as well. The articles though, I was able to fix by filling in the missing details. I cannot do that for the runbooks becuase their mandatory 'article' field gives me no results. I can confirm the target articles are published in the instance, I have even tried to copy an article's sysid to no avail.

Now, I've looked into the url results and found that what causes no results to appear is the query condition: sysparm_form_view=default. Aside from that however, I don't see what else it could be.

Has anyone else had this issue? What can i do to fix this?

[Mark Manders]

What do you mean with the knowledge articles port over empty? How are you moving them at all? It's data, so the best way to create them, would be on PROD. In case they are needed to develop other stuff, you could push them to an update set or move them through XML, but that would have the sysIDs as the same and should reflect in your runbooks as well.

[JulienRouge1549]

We currently aren't on Prod at the moment. In regards to moving the articles, I've imported them using the import action

.
Regarding  pushing through updates and xml. I chose the import feature and brought them in as xcel documents. Could that be the source of the issue?

[JulienRouge1549]

So, I figured out a solution. It turns out that the ui action for runbook creation was restricted to a certain knowledge base so, when I removed the that part of the condition, I was able to recreate them on the instance. So my issue has been solved but I have to ask, is there a better way?