I'm pretty sure you just want <module name="Search"> <param name="search">"$row.fields.pp_msgid$"</param> </module> You don't need to mess around with CDATA - that's actually for xml-unsafe characters in the param string, not for characters in the evaluated $foo$ token. ... View more

From a module's JS you can get the module id just with this.moduleId . What's unusual about it is that the property is assigned by ModuleLoader as it's initializing the modules. This is why you don't see much or any evidence of the property existing or being initialized in the module class itself. And one other thing that can be problematic, is that the property is not actually defined in the initialize() function, and therefore also not in any functions called during initialize . ModuleLoader doesn't assign the property until the module is constructed, ie until initialize returns. This can be problematic if you really do need to do something when the module is constructed, and sometimes you need to take the last resort of using a setTimeout with a second argument of 0. That will basically defer the execution of the function you're calling in the timeout until after the ModuleLoader's work is done. And given your "_chart" suffix, the select statement would be d3.select('#' + this.moduleId + '_chart svg') ... View more

I think it's just because you're wrapping the condition in single quotes? So the "condition" you're asking it to evaluate is just a big string. Strings evaluate to true in a boolean context in JS, so it's doing so here and thus always picking the first child. Remove the single quotes and it should be fine. Since you're using Sideview Utils in this view, you may want to look into replacing Splunk's ConditionalSwitcher module with the simple conditional abilities of the Sideview ValueSetter module in combination with the Sideview Switcher module. This can give you more flexibility than the old ConditionalSwitcher, which could only switch between one or two branches. http://sideviewapps.com/apps/sideview-utils UPDATE: Aha!. The other problem is that the way ConditionalSwitcher is implemented, it will only ever check the condition in two cases 1) When the module receives a push from upstream, and 2) when the currently running job it has access to has made some progress towards completion - (in this case it will only check if the condition param has "job" anywhere in it) In your example there is no push from above (eg via an autoRun="True" attribute upstream), and so the ConditionalSwitcher actually never checks it's condition so the first child remains selected simply because it's selected by default. You can rework the example a bit to have an autoRun="True" on a module upstream somewhere and it will start working. Here is a modified view. <view onunloadCancelJobs="true" template="dashboard.html"> <label>ConditionalSwitcher Test</label> <module name="AccountBar" layoutPanel="appHeader" /> <module name="SideviewUtils" layoutPanel="appHeader" /> <module name="AppBar" layoutPanel="appHeader" /> <module name="Message" layoutPanel="messaging"> <param name="filter">*</param> <param name="maxSize">2</param> <param name="clearOnJobDispatch">False</param> </module> <!-- if 1 = 0 --> <module name="URLLoader" layoutPanel="panel_row1_col1" autoRun="True"> <module name="ConditionalSwitcher"> <param name="mode">independent</param> <param name="condition">"1"=="0"</param> <!-- then true --> <module name="HTML"> <param name="html"> First </param> </module> <!-- else false --> <module name="HTML"> <param name="html"> Second </param> </module> </module> </module> <!-- end ifs --> </view> ... View more

I think it's just a typo in your view. There is indeed no param on the Search module called "lastest" - but I think you intended to set the "latest" param. So somewhere on the page, I think there's at least one Search module with a typo in its earliest param? ... View more

You're right. The reason why the switcher is only showing and hiding the "report1" section is that the "report2" section is not a child of the switcher at all. Especially on a view this complicated (or half this complicated), you need to be very careful with your indentation so as to minimize your own confusion. If the file was indented cleanly, it would have been easy for you to spot the misalignment - the fact that "report1" and "report2" were not siblings of eachother. There's basically an extra </module> tag before the "report2" section, that you'll have to move to the end of that same section. However... there's a lot else that is quite wrong with this approach and there's a lot of dead stuff in this view that can be removed. I've taken the liberty of cleaning it all up and posting the result to pastebin. The cleaned up version is half the size. http://pastebin.com/xtZRVU8X 1) The only difference between the report1 section and the report2 section, is that the first does chart avg(duration) by PAGE COMMON_TASK and the second does | timechart avg(duration) by PAGE . Just have those be the two values of your Pulldown, and dont use the Switcher module at all. Switcher should be a last resort, for when you have some difference between sections where the module config per section has to be fundamentally different. Here you can factor the difference into a single $foo$ token. This will drastically simplify your view. 2) You're setting searchWhenChanged to False on the TimeRangePicker even though you have allowSoftSubmit to False on the SubmitButton. Change searchWhenChanged to True (you should quite honestly never use False ever. it is kind of evil and the UI can behave badly) 3) lots of dead or vestigial module code. a) I strongly suspect that your ViewstateAdapter module is actually serving no purpose and it has just been copied over from some original simpleXML conversion long ago. Delete it entirely b) HiddenFieldPicker and Gimp are definitely doing nothing, and are vestigial carryovers from simpleXML conversion. Delete them. c) JobProgressIndicator and EnablePreview should never contain downstream modules (it does no harm but it makes no sense). This is a bug in the SimpleXML conversion code. De-indent these child modules. Save your eyesight a little. 4) weird things on the <view> tag. Some of these are side effects of simplexml conversion, but you can delete autoCancelInterval="90" isVisible="true" objectMode="SimpleForm" and also autorun="False" . Some of those are defaults and some are having no effect. 5) updatePermalink on the SubmitButton module isn't going to be doing anything useful so you can remove it. However... if you want a permalink to be constantly updated, even in an arbitrary form search view in advanced XML like this, you can use the Sideview URLLoader module with the keepUrlUpdated param set to true, and it will actually update a working permalink as well as enable back button and forward button for all the pulldown changes. 6) the groupLabel param is meaningless and it's just cruft accidentally inserted by the simpleXml conversion code. You can delete all of these. 7) lots of duplicated layoutPanel attributes. If layoutPanel is specified for a given module, all its downstream modules will inherit that layoutPanel so there's no need to specify it again. 😎 I'm fairly certain that many of your charting keys were explicitly setting values that happen to be the default values for the given key in the charting framework, so I removed those. In the end your XML becomes a LOT simpler with all these fixes and cleanups. For some reason the answers site is being a bit ornery with respect to posting large code samples, so I've put a cleaned up version over in pastebin for you. http://pastebin.com/xtZRVU8X One more note - a useful and cheap trick to perfectly indent a crazily-indented view, is to load that view in the Sideview Editor, then pick something at random to edit. Submit the form however with the exact values that it loaded with. The Sideview Editor will write the XML back to disk, but it will do lots of little cleanup things to it and one of those is that the indentation will get fixed. You might have to fish the file out of local and move ti over to default, but it can be useful. ... View more

Yes - the name of the query string arg has to match the "name" param of the Checkbox module, and the value of the arg has to match either the "onValue" param or the "offValue" param. I would just double check that when you tried your ?checkboxName=onValue URL, that the Checkbox module indeed had those exact values in its config, ie: <param name="name">checkboxName</param> <param name="onValue">onValue</param> I thought I remembered something in the release notes in this general area but there isn't anything there, so I'll water that thought down to a general precaution to make sure you're on a current Sideview Utils. Current version is 3.2.1 release notes - http://sideviewapps.com/apps/sideview-utils/release-notes/ mailing list - http://sideviewapps.com/apps/sideview-utils/mailing-list/ everything you wanted to know about Sideview Utils licensing - http://sideviewapps.com/apps/sideview-utils/licensing-faq/ ... View more