Join the Conversation
- Find Answers
- :
- Using Splunk
- :
- Dashboards & Visualizations
- :
- Re: Token Not Working when Adding JSON Values
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
Hoping for some help, I have a simple Dashboard that allows a user to select specific geography to return results for that geo. The search is based off of a SQL query and uses tokens to determine the correct geography.
The report has been working perfectly for a long time, recently we had an upgrade to our application that added JSON columns to our DB and moved some of the fields I was returning into the JSON clob data field.
I updated the query to extract the necessary JSON fields, which works, however, now after adding the JSON details to the query, the token is no longer working. I keep getting "Search is Waiting for Input".
I have tried to move the connection argument, before and after the SQL query, see below, neither seemed to
work.
| dbxquery query="blah blah" connection=geography
| dbxquery connection=geography query="blah blah"
Hoping someone can point out what I need to add or update, so that the token is recognized/working again.
Thank you in advance for any assistance.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Would it be possible to share some sample data and part of your dashboard xml ?
It could be due to various issues including presence of a $ sign in your data which needs to be escaped while using in token.
What goes around comes around. If it helps, hit it with Karma 🙂
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Would it be possible to share some sample data and part of your dashboard xml ?
It could be due to various issues including presence of a $ sign in your data which needs to be escaped while using in token.
What goes around comes around. If it helps, hit it with Karma 🙂
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Sorry for the delay in responding. You have helped me immensely.
That indeed was the issues. Thank you so much for the help!
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@g038123, glad it worked.
Appreciate if you could upvote ( 👍 ) and accept it as a solution to close the thread.
What goes around comes around. If it helps, hit it with Karma 🙂
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas
What Is the Name of the USB Key Inserted by Bob Smith? (BOTS Hint, Not the Answer)
Automating Threat Operations and Threat Hunting with Recorded Future
