All Apps and Add-ons

ValueSetter Module with Url Loader Module

cmak
Contributor

I have some pulldowns that I would like to prepopulate. I would like to prepopulate my pulldowns based on the URL parameters. However, if there are no URL params, I would like to have a default value for the pulldowns so they are not empty. It seems like I should be using URLLoader with the ValueSetter module.

However, it seems that these two modules conflict with each other. The downstream module would take precedence.

If the URL loader is downstream from the Valuesetter module and no URL parameters are passed, then no pulldown selections will be made.

If the ValueSetter module is downstream from the URL Loader, then the default values will always be chosen.

Is there a way to fix this behavior?

1 Solution

sideview
SplunkTrust
SplunkTrust

This is what the allowClobber param is for, on the ValueSetter module.

Put your ValueSetter module downstream from the URLLoader and upstream from your Pulldown, give the ValueSetter the same "name" as the Pulldown, which is in turn the same name as the argument name from the URL. But set the 'allowClobber' param on the ValueSetter to "False".

This will mean that the ValueSetter will only send its value when there is no value coming from the URLLoader.

View solution in original post

sideview
SplunkTrust
SplunkTrust

This is what the allowClobber param is for, on the ValueSetter module.

Put your ValueSetter module downstream from the URLLoader and upstream from your Pulldown, give the ValueSetter the same "name" as the Pulldown, which is in turn the same name as the argument name from the URL. But set the 'allowClobber' param on the ValueSetter to "False".

This will mean that the ValueSetter will only send its value when there is no value coming from the URLLoader.

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...