Dashboards & Visualizations

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

blurblebot
Communicator

Though this has been discussed on Splunk Answers, the prevailing solution has not worked for me.

As per the discussions on Splunk Answers, I've switched the "intention" and "replacementMap" params in my xml, but as soon as I populate the search field, the error is thrown. If I leave it blank, it uses the default value from the xml, but that's as much luck as I can wrangle.

Below is the EFS section modified as per prevailing recommendations:

<module name="ExtendedFieldSearch"
layoutPanel="viewHeader">
     <param name="intention">
     <param name="name">stringreplace</param>
     <param name="arg">
    <param name="sourcetypeToken">
       <param name="default">*</param>
       <param name="fillOnEmpty">True</param>
     </param>
   </param>
 </param>   <param name="replacementMap">
   <param name="arg">
     <param name="sourcetypeToken"/>
   </param>
 </param>
 <param name="field">sourcetype</param>
 <param name="q">splunkd</param> 

...

Tags (1)
1 Solution

gkanapathy
Splunk Employee
Splunk Employee

You are right that the "accepted" answer here is wrong. However, the other upvoted answer by dmlee is correct.

Swapping the sections I would not expect to have any effect. However, your replacmentMap arg needs a value:

<module name="ExtendedFieldSearch" layoutPanel="viewHeader">
  <param name="intention">
    <param name="name">stringreplace</param>
    <param name="arg">
      <param name="sourcetypeToken">
        <param name="default">*</param>
        <param name="fillOnEmpty">True</param>
      </param>
    </param>
  </param>   
  <param name="replacementMap">
    <param name="arg">
      <param name="sourcetypeToken">
        <param name="value"></param>
      </param>
    </param>
  </param>
  <param name="field">sourcetype</param>
  <param name="q">splunkd</param> 

View solution in original post

gkanapathy
Splunk Employee
Splunk Employee

You are right that the "accepted" answer here is wrong. However, the other upvoted answer by dmlee is correct.

Swapping the sections I would not expect to have any effect. However, your replacmentMap arg needs a value:

<module name="ExtendedFieldSearch" layoutPanel="viewHeader">
  <param name="intention">
    <param name="name">stringreplace</param>
    <param name="arg">
      <param name="sourcetypeToken">
        <param name="default">*</param>
        <param name="fillOnEmpty">True</param>
      </param>
    </param>
  </param>   
  <param name="replacementMap">
    <param name="arg">
      <param name="sourcetypeToken">
        <param name="value"></param>
      </param>
    </param>
  </param>
  <param name="field">sourcetype</param>
  <param name="q">splunkd</param> 

r999
Path Finder

what have you changed? only added

?

0 Karma
Get Updates on the Splunk Community!

[Puzzles] Solve, Learn, Repeat: Dynamic formatting from XML events

This challenge was first posted on Slack #puzzles channelFor a previous puzzle, I needed a set of fixed-length ...

Enter the Agentic Era with Splunk AI Assistant for SPL 1.4

  &#x1f680; Your data just got a serious AI upgrade — are you ready? Say hello to the Agentic Era with the ...

Stronger Security with Federated Search for S3, GCP SQL & Australian Threat ...

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...