https://community.splunk.com/t5/Dashboards-Visualizations/What-does-objectMode-mean-for-a-view/m-p/54054#M2809 <P>"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. **</P> <P>Technically 'ObjectMode' will have a single small effect -- the view will get an extra CSS class of "splFormSearch" written to the <CODE>&lt;body&gt;</CODE> tag. However since you can achieve the same specificity in a custom app by using custom stylesheets or even using the <CODE>.splView-VIEWNAME</CODE> selector, this doesnt really add anything. </P> <P>** By the way you can see a more thorough writeup of these in this answer: <A href="http://splunk-base.splunk.com/answers/13565/multiple-forms-with-an-input-field-and-timerangepicker-no-repeat-input">http://splunk-base.splunk.com/answers/13565/multiple-forms-with-an-input-field-and-timerangepicker-no-repeat-input</A></P> Wed, 21 Sep 2011 02:24:48 GMT sideview 2011-09-21T02:24:48Z https://community.splunk.com/t5/Dashboards-Visualizations/What-does-objectMode-mean-for-a-view/m-p/54053#M2808 <P>Can anyone help explain what the "objectMode" attribute is used for when defining an advanced XML view?</P> <P>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?</P> <P>Example:</P> <PRE><CODE> &lt;view autoCancelInterval="90" isVisible="false" objectMode="SimpleForm" onunloadCancelJobs="true" template="dashboard.html"&gt; </CODE></PRE> Fri, 05 Aug 2011 13:26:37 GMT https://community.splunk.com/t5/Dashboards-Visualizations/What-does-objectMode-mean-for-a-view/m-p/54053#M2808 Lowell 2011-08-05T13:26:37Z https://community.splunk.com/t5/Dashboards-Visualizations/What-does-objectMode-mean-for-a-view/m-p/54054#M2809 <P>"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. **</P> <P>Technically 'ObjectMode' will have a single small effect -- the view will get an extra CSS class of "splFormSearch" written to the <CODE>&lt;body&gt;</CODE> tag. However since you can achieve the same specificity in a custom app by using custom stylesheets or even using the <CODE>.splView-VIEWNAME</CODE> selector, this doesnt really add anything. </P> <P>** By the way you can see a more thorough writeup of these in this answer: <A href="http://splunk-base.splunk.com/answers/13565/multiple-forms-with-an-input-field-and-timerangepicker-no-repeat-input">http://splunk-base.splunk.com/answers/13565/multiple-forms-with-an-input-field-and-timerangepicker-no-repeat-input</A></P> Wed, 21 Sep 2011 02:24:48 GMT https://community.splunk.com/t5/Dashboards-Visualizations/What-does-objectMode-mean-for-a-view/m-p/54054#M2809 sideview 2011-09-21T02:24:48Z