All Apps and Add-ons

When redirecting from a drilldown, why is testfield in redirect not correct on tables with multiple rows?

subtrakt
Contributor

Hi,

This below config is not redirecting with the correct field if more than one row exists on the table. I have a feeling I'm missing something simple.

<param name="fields">testfield</param>

  <module name="Redirector">

    <param name="url">flashtimeline</param>

    <param name="popup">True</param>

    <param name="arg.earliest">-8h</param>

    <param name="arg.latest">$search.timeRange.latest$</param>

    <param name="arg.q">index=testindex "$click.value2$" testfield="$testfield$</param>

        </module>

        </module>

        </module>

        </module>

        </module>
0 Karma
1 Solution

sideview
SplunkTrust
SplunkTrust

1) It's a little weird to use $click.*$ tokens if you're using Sideview Utils, because the Sideview tokens are a lot more intuitive and flexible. If the first column in your table is "user", then I would replace $click.value2$ with $click.fields.user$. It will work the same; it's just easier to understand.

2) At first I thought with $testfield$, that you weren't intending that to incorporate anything from the drilldown row, but perhaps you are? If so, if there's a column called "testfield" in the results, then you want $click.fields.testfield$.

If I had to guess, I'd say the "it works for only one row" mystery is somehow related to there being a form element module upstream whose name is actually "testfield".

View solution in original post

sideview
SplunkTrust
SplunkTrust

1) It's a little weird to use $click.*$ tokens if you're using Sideview Utils, because the Sideview tokens are a lot more intuitive and flexible. If the first column in your table is "user", then I would replace $click.value2$ with $click.fields.user$. It will work the same; it's just easier to understand.

2) At first I thought with $testfield$, that you weren't intending that to incorporate anything from the drilldown row, but perhaps you are? If so, if there's a column called "testfield" in the results, then you want $click.fields.testfield$.

If I had to guess, I'd say the "it works for only one row" mystery is somehow related to there being a form element module upstream whose name is actually "testfield".

subtrakt
Contributor

You are right. $click.fields.user$ is the solution. Many Thanks!

sideview
SplunkTrust
SplunkTrust

Can you include the module and param tags for the Table/SimpleResultsTable ?

0 Karma

subtrakt
Contributor
<module name="Paginator">
            <param name="count">10</param>
            <param name="entityName">results</param>
<module name="SimpleResultsTable">
<param name="entityName">results</param>
<param name="drilldown">row</param>    
0 Karma
Get Updates on the Splunk Community!

What's new in Splunk Cloud Platform 9.1.2312?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.1.2312! Analysts can ...

What’s New in Splunk Security Essentials 3.8.0?

Splunk Security Essentials (SSE) is an app that can amplify the power of your existing Splunk Cloud Platform, ...

Let’s Get You Certified – Vegas-Style at .conf24

Are you ready to level up your Splunk game? Then, let’s get you certified live at .conf24 – our annual user ...