Refine your search:

(NOTE - I have read other similar posts and solutions have not helped)

I have a created a dashboard with 2 text boxes for a search. The default value if nothing enetered is "*".

This worked well until i needed to add a radio button to the search options and i was forced to convert to advanced XML.

Now i have converted all works well if i leacve text boxes empty and the search uses the *, but if anything entered into text boxes i get the error below:

PARSER: Applying intentions failed 'unicode' object has no attribute 'get'

'unicode' object has no attribute 'get' on Splunk Answers This one states to add the line

<param name="value"></param>

This does not fix issue. It also says to change the order round- this does nto seem to work either! my code:

 <module name="ExtendedFieldSearch">
      <param name="replacementMap">
        <param name="arg">
          <param name="Group"/>
              </param>
          </param>
      <param name="field">Enter ’Group' name</param>
      <param name="intention">
        <param name="name">stringreplace</param>
        <param name="arg">
          <param name="Group">
            <param name="default">*</param>
            <param name="fillOnEmpty">True</param>
          </param>
        </param>
      </param>

      <module name="ExtendedFieldSearch">
        <param name="replacementMap">
          <param name="arg">
            <param name="UserAddedRemoved"/>
                </param>
        </param>
        <param name="field">Enter 'Username'</param>
        <param name="intention">
          <param name="name">stringreplace</param>
          <param name="arg">
            <param name="UserAddedRemoved">
              <param name="default">*</param>
              <param name="fillOnEmpty">True</param>
            </param>
          </param>
        </param>

let me know if you need more?

Please do not just point me to another post as none of them clearly identify what needs changing

asked 28 Jun '12, 04:48

r999's gravatar image

r999
20116
accept rate: 0%

edited 28 Jun '12, 04:48


One Answer:

The question you linked has the answer. In the replacementMap sections, where your XML says


<param name="UserAddedRemoved"/>
you need to change it to


<param name="UserAddedRemoved">
  <param name="value"></param>
</param>

It's not just adding the value param line; you have to remove the trailing / from the name=UserAddedRemoved line to ensure the value definition is part of the correct parent block. Same goes for the Group replacement map section. I copied your XML into a test view and verified that it worked with these changes. (It also wanted me to add a layoutPanel parameter to the ExtendedFieldSearch module definition, but that's a quick fix.)

link

answered 19 Sep '12, 10:56

cphair's gravatar image

cphair
98326
accept rate: 51%

Post your answer
toggle preview

Follow this question

Log In to enable email subscriptions

RSS:

Answers

Answers + Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "Title")
  • image?![alt text](/path/img.jpg "Title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×469
×5
×5
×5
×2

Asked: 28 Jun '12, 04:48

Seen: 601 times

Last updated: 19 Sep '12, 10:56

Copyright © 2005-2012 Splunk Inc. All rights reserved.