All Apps and Add-ons

When imported the Lookup file with the Looup editor, some records become NaN

Watanabe
New Member

I imported the lookup file using the app Lookup Editor.
The record of the column whose column name is only numbers was NaN.
(Normal values are values such as 1A or 4A etc, but those values are all NaN after import)

Currently, we were able to update with the following measures.
1. Change the column name of only the numerical value of the file before import to a character string and import it.
2. After importing, change to the correct column name.

Since this correspondence is a provisional correspondence, I would like to solve the problem that the record changes to NaN.

Sorry, If there are people who know how to solve this problem, please reply.

Lookup Editor
version:3.4.6
build:1595011574

Kind Regards,

Labels (1)
Tags (1)
0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Tech Talk Recap | Mastering Threat Hunting

Mastering Threat HuntingDive into the world of threat hunting, exploring the key differences between ...

Observability for AI Applications: Troubleshooting Latency

If you’re working with proprietary company data, you’re probably going to have a locally hosted LLM or many ...

Splunk AI Assistant for SPL vs. ChatGPT: Which One is Better?

In the age of AI, every tool promises to make our lives easier. From summarizing content to writing code, ...