Reporting

Treating comma separated values as numbers in Pivot data model attribute definition

gregbujak
Path Finder

This question is specific to the new Pivot functionality in Splunk 6.

I have built up my data model, defined all the attributes and am ready to crunch my data.
However, I have a field/attribute (notional) that is a numeric field with comma formatting (ex. 1,000,000).

What is the process for eliminating the comma so that I can properly define it as a number?

I understand how to do this in regular search but cant figure out the secret sauce for pivot.

Thanks

0 Karma

Simon_Fishel
Splunk Employee
Splunk Employee

In the data model editor, you should be able to define an Eval attribute and do whatever you would do in regular search.

gregbujak
Path Finder

You are correct in a very general way.
Following:
http://answers.splunk.com/answers/36792/how-to-sum-numbers-with-commas
Using rex: "(?.)" | convert rmcomma(stripped_notional)
The result was empty.
Using rex: setting field to notional
"(?.
)"| rex field=stripped_notional mode=sed "s/,//g"
Caused a parse error in "//g"

Using eval: setting field to stripped_notional and then the eval expression: replace(notional, ",", "")
finally worked.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Event Series: The Agentic SOC: Trust Before Autonomy

AI is fundamentally changing security operations, but true progress requires more than just automation—it ...

Free Professional Services for .conf26 Attendees

This year at .conf26, we are doing something a little different. We are bringing the best minds from ...

Defend at Machine Speed: Your Guide to Security Sessions at .conf26

Splunk .conf26   With threats moving at machine speed and attack surfaces expanding across hybrid ...