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
Get Updates on the Splunk Community!

Accelerating Observability as Code with the Splunk AI Assistant

We’ve seen in previous posts what Observability as Code (OaC) is and how it’s now essential for managing ...

Integrating Splunk Search API and Quarto to Create Reproducible Investigation ...

 Splunk is More Than Just the Web Console For Digital Forensics and Incident Response (DFIR) practitioners, ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...