topic Re: Is it possible to loadjob a post-processed search? in Dashboards & Visualizations

Is it possible to loadjob a post-processed search?

nick405060 — Wed, 30 Sep 2020 00:22:58 GMT

Hi guys,

Loadjob $post_process_search$ only loads $base_search$ data and not anything from the post-process search? Why? I understand it probably has something to do with how the $job.sid$ token is passed between the base and post-process search, but not more than that. How do I fix this?

  <search id="vpn_base">
    <query>
...
    </query>
    <done>
      <condition>
        <set token="base_search">$job.sid$</set>
      </condition>
    </done>
  </search>
  <search base="vpn_base">
    <query>
...
    </query>
    <done>
      <condition>
        <set token="post_process_search">$job.sid$</set>
      </condition>
    </done>
  </search>

Re: Is it possible to loadjob a post-processed search?

nick405060 — Tue, 07 May 2019 23:47:15 GMT

I would still like to know a "yes" answer to this question.

However, the obvious workaround is just to | makeresults | append [| loadjob "$base_search$"] in the now-pseudo post-process query and do away with any base setting/referencing, keeping the post_process_search token.

But it would be great to know a true answer, considering this is just a workaround and no longer includes a true post-process search. Even if you take away base_search in the original example, loadjobbing post_process_search still just loads the base search data.

Re: Is it possible to loadjob a post-processed search?

woodcock — Tue, 07 May 2019 23:58:25 GMT

In your post-process search add this to the end:

| addinfo | rename info_* AS _info_*

Then you can access $result._info_sid$ to get it.

Re: Is it possible to loadjob a post-processed search?

nick405060 — Wed, 08 May 2019 19:07:24 GMT

This does not work. $result._info_sid$ still loads the base search.

Re: Is it possible to loadjob a post-processed search?

woodcock — Wed, 08 May 2019 20:04:00 GMT

Wow. That is shocking. I would open a support case because that makes no sense and really should be treated as a bug and fixed.

The reason to use an underscore is so that it is invisible in the panel and search results, but still available for us to use (it would be confusing to the users).