Dashboards & Visualizations

What does objectMode mean for a view?

Lowell
Super Champion

Can anyone help explain what the "objectMode" attribute is used for when defining an advanced XML view?

I've seen a few different options, like "SimpleForm", and "viewconf", but I can't tell what difference this makes? How do you know which one to pick?

Example:

 <view autoCancelInterval="90" isVisible="false" objectMode="SimpleForm" onunloadCancelJobs="true" template="dashboard.html">
Tags (3)
1 Solution

sideview
SplunkTrust
SplunkTrust

"objectMode" is a vestige from when the view (or one of its ancestors) was converted from the Simplified XML format. There's a number of things that get swept along with this conversion like 'groupLabel' params which can all be safely deleted. Then there's a bunch of other things like HiddenFieldPicker and ViewStateAdapter that can be safely deleted 99% of the time. There's also some strange indentation it does - for example you'll find modules nested inside JobProgressIndicator modules and inside EnablePreview modules which serves no purpose besides making the XML harder to read. **

Technically 'ObjectMode' will have a single small effect -- the view will get an extra CSS class of "splFormSearch" written to the <body> tag. However since you can achieve the same specificity in a custom app by using custom stylesheets or even using the .splView-VIEWNAME selector, this doesnt really add anything.

** By the way you can see a more thorough writeup of these in this answer: http://splunk-base.splunk.com/answers/13565/multiple-forms-with-an-input-field-and-timerangepicker-n...

View solution in original post

sideview
SplunkTrust
SplunkTrust

"objectMode" is a vestige from when the view (or one of its ancestors) was converted from the Simplified XML format. There's a number of things that get swept along with this conversion like 'groupLabel' params which can all be safely deleted. Then there's a bunch of other things like HiddenFieldPicker and ViewStateAdapter that can be safely deleted 99% of the time. There's also some strange indentation it does - for example you'll find modules nested inside JobProgressIndicator modules and inside EnablePreview modules which serves no purpose besides making the XML harder to read. **

Technically 'ObjectMode' will have a single small effect -- the view will get an extra CSS class of "splFormSearch" written to the <body> tag. However since you can achieve the same specificity in a custom app by using custom stylesheets or even using the .splView-VIEWNAME selector, this doesnt really add anything.

** By the way you can see a more thorough writeup of these in this answer: http://splunk-base.splunk.com/answers/13565/multiple-forms-with-an-input-field-and-timerangepicker-n...

Get Updates on the Splunk Community!

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...

Updated Team Landing Page in Splunk Observability

We’re making some changes to the team landing page in Splunk Observability, based on your feedback. The ...

New! Splunk Observability Search Enhancements for Splunk APM Services/Traces and ...

Regardless of where you are in Splunk Observability, you can search for relevant APM targets including service ...