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 (2)
Tags (1)
0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...