All Apps and Add-ons

default search * being dispatched unintentionally

subtrakt
Contributor

Hi Everyone,
Everything works as intended with this view including the radio selections. However, i'm having a problem with second search * being dispatched on top of the regular search module..

Is this because the radio module is a dispatch module? Can i stop the radio module from dispatching search *? If i take out the radio module the search * doesn't occur.

<module name="Button" layoutPanel="panel_row3_col1">
 <param name="allowSoftSubmit">False</param>
 <param name="allowAutoSubmit">False</param>
            <param name="label">SUBMIT</param>   

            <module name="TextField" layoutPanel="panel_row3_col1">
                <param name="name">DESCRIPTION</param>
                <param name="label">Description:</param>
                <param name="width">602px</param>

                <module name="TextField" layoutPanel="panel_row3_col1">
                    <param name="name">EXPERIENCE</param>
                    <param name="label">EXPERIENCE</param>
                    <param name="width">602px</param>


                    <module name="TextField" layoutPanel="panel_row3_col1">
                        <param name="name">TICKET</param>
                        <param name="label">Ticket:</param>
                        <param name="width">60px</param>

                        <module name="TextField" layoutPanel="panel_row3_col1">
                            <param name="name">FLOW</param>
                            <param name="label">Flow:</param>
                            <param name="width">200px</param>

                        <module name="Radio" layoutPanel="panel_row2_col1" autoRun="false">
                                <param name="name">TEST</param>
                                <param name="staticRadios">
                                    <list>
                                        <param name="label">TEST1</param>
                                        <param name="value">TEST1</param>
                                    </list>
                                    <list>
                                        <param name="label">TEST2</param>
                                        <param name="value">TEST2</param>
                                    </list>
                                </param>
                                                        <module name="Search" layoutPanel="panel_row4_col1">
                                <param name="search">...
1 Solution

sideview
SplunkTrust
SplunkTrust

This is a bug in the Radio module. I'm sorry about the inconvenience and thank you for posting this.

I'll try and accelerate the next maintenance release so that it can happen this week. Subscribe to the release notes mailing list if you haven't already here - http://sideviewapps.com/apps/sideview-utils/mailing-list/

PS. if are feeling a great excess of confidence, it is a single-character fix.
In sideview_utils/appserver/modules/Radio/Radio.js on line 75 you'll see:

requiresResults: function() {
    return (this.searchFields.length>=0);
},

it should be >0 and not >=0. Delete the "=", save the file and then either clear your browser cache or hit the bump button.

The bug makes the Radio module think it always has dynamic radios configured, and it makes it trigger a dispatch if there isn't already a dispatched search there.

View solution in original post

sideview
SplunkTrust
SplunkTrust

This is a bug in the Radio module. I'm sorry about the inconvenience and thank you for posting this.

I'll try and accelerate the next maintenance release so that it can happen this week. Subscribe to the release notes mailing list if you haven't already here - http://sideviewapps.com/apps/sideview-utils/mailing-list/

PS. if are feeling a great excess of confidence, it is a single-character fix.
In sideview_utils/appserver/modules/Radio/Radio.js on line 75 you'll see:

requiresResults: function() {
    return (this.searchFields.length>=0);
},

it should be >0 and not >=0. Delete the "=", save the file and then either clear your browser cache or hit the bump button.

The bug makes the Radio module think it always has dynamic radios configured, and it makes it trigger a dispatch if there isn't already a dispatched search there.

subtrakt
Contributor

Thank you sir!

0 Karma

sideview
SplunkTrust
SplunkTrust

Can you post the full XML, or email it to me at support@sideviewapps.com Thanks.
I don't think it can be the Radio button, since the Radio is configured only with staticRadios. However you're right it sounds pretty incriminating. I'm thinking that there will be some other detail in the overall view, not in the XML pasted here, that will shed a lot more light.

0 Karma

subtrakt
Contributor
<view autoCancelInterval="1" decomposeIntentions="false" isPersistable="true" isSticky="true" isVisible="true" nativeObjectMode="viewconf" objectMode="SimpleDashboard" onunloadCancelJobs="true" template="dashboard.html" type="module">
    <label>test</label>
    <module name="AccountBar" layoutPanel="appHeader" />
    <module name="SideviewUtils" layoutPanel="appHeader" />
    <module name="DashboardTitleBar" layoutPanel="viewHeader" />



    <module name="URLLoader" layoutPanel="viewHeader" autoRun="true">


        <module name="HTML" layoutPanel="panel_row1_col1">
            <param name="html"><![CDATA[<b>Item:</b> $ERROR$ <br>&lt;br/&gt;<b>APP:</b> $APP$]]></param>
        </module>


        <module name="Button" layoutPanel="panel_row3_col1">
 <param name="allowSoftSubmit">False</param>
 <param name="allowAutoSubmit">False</param>
            <param name="label">SUBMIT</param>   

            <module name="TextField" layoutPanel="panel_row3_col1">
                <param name="name">DESCRIPTION</param>
                <param name="label">Description:</param>
                <param name="width">602px</param>

                <module name="TextField" layoutPanel="panel_row3_col1">
                    <param name="name">EXPERIENCE</param>
                    <param name="template">$EXPERIENCE$</param>
                    <param name="label">EXPERIENCE</param>
                    <param name="width">602px</param>


                    <module name="TextField" layoutPanel="panel_row3_col1">
                        <param name="name">TICKET</param>
                        <param name="label">Ticket:</param>
                        <param name="width">60px</param>

                        <module name="TextField" layoutPanel="panel_row3_col1">
                            <param name="name">FLOW</param>
                            <param name="label">Flow:</param>
                            <param name="width">200px</param>


                            <module name="ValueSetter">
                                <param name="name">WAIT</param>
                                <param name="value">Please wait...</param>

                                <module name="HTML" layoutPanel="panel_row4_col1">
                                    <param name="html"><![CDATA[<font color="green"><b>$WAIT$</b></font>]]></param>
                                </module>
                            </module>



                            <module name="Radio" layoutPanel="panel_row2_col1" autoRun="false">
                                <param name="name">IMPACT</param>
                                <param name="staticRadios">
                                    <list>
                                        <param name="label">Impact</param>
                                        <param name="value">Impact</param>
                                    </list>
                                    <list>
                                        <param name="label">Ignore</param>
                                        <param name="value">No Impact</param>
                                    </list>
                                    <list>
                                        <param name="label">Monitor</param>
                                        <param name="value">Monitor</param>
                                        <param name="selected">true</param>
                                    </list>
                                    <list>
                                        <param name="label">Impact Pending Review</param>
                                        <param name="value">Impact Pending Review</param>
                                    </list>
                                    <list>
                                        <param name="label">Other</param>
                                        <param name="value">Other</param>

                                    </list>
                                </param>

                                <!--appends token values to the lookup--> 
                                <module name="Search" layoutPanel="panel_row4_col1">

                                    <param name="search">
                                        <![CDATA[| stats count 
| eval ERROR=$ERROR$
| eval APP=$APP$ 
| eval EXPERIENCE="$IMPACT$ - $EXPERIENCE$"
| eval DESCRIPTION="$DESCRIPTION$"  
| eval ENTRY_DATE=now() | eval ENTRY_DATE=strftime(ENTRY_DATE,"%D %T")
| eval TICKET="$TICKET$" 
| eval FLOW="$FLOW$"
| table ERROR APP EXPERIENCE DESCRIPTION TICKET FLOW WHO ENTRY_DATE
| join [| rest /services/authentication/users splunk_server=local | rename email AS WHO | fields WHO]
| outputlookup append=true known_errors.csv
]]>
                                    </param>


                                    <module name="Table">
                                                                      </module>
                                </module>
                            </module>
                        </module>
                    </module>
                </module>
            </module>
        </module>
    </module>

</view>
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

[Puzzles] Solve, Learn, Repeat: Matching cron expressions

This puzzle (first published here) is based on matching timestamps to cron expressions.All the timestamps ...

Design, Compete, Win: Submit Your Best Splunk Dashboards for a .conf26 Pass

Hello Splunkers,  We’re excited to kick off a Splunk Dashboard contest! We know that dashboards are a primary ...

May 2026 Splunk Expert Sessions: Security & Observability

Level Up Your Operations: May 2026 Splunk Expert Sessions Whether you are refining your security posture or ...