Known issues
Version 4.0.5
The following are known issues in the Splunk App for Lookup File Editing. If no known issues are listed, then no issues have been reported.
Date filed | Issue number | Description |
---|---|---|
2025-03-18 | LOOKUP-304 | Unable to Update KV Store Lookups in Splunk App for Lookup File Editor (v4.0.5) |
2025-02-14 | LOOKUP-300 | Not able to remove records from the CSV lookup file in Splunk App for Lookup File Editing version 4.0.5 |
Version 4.0.4
Date filed | Issue number | Description |
---|---|---|
2024-05-21 | LOOKUP-255 | The app duplicates rows for the same record if you create a KV store lookup and copy-paste records from a CSV file to the lookup |
2024-08-21 | LOOKUP-284 | When you create a CSV lookup file and use any supported delimiters other than a comma in a single cell, then you can't import that same lookup file after you export it in the Splunk App for Lookup File Editing. |
Version 4.0.2
Date filed | Issue number | Description |
---|---|---|
2024-08-21 | LOOKUP-284 | issue while using supported delimiters (other than comma) in a single cell |
2024-05-12 | LOOKUP-253 | Lookup list pagination shows incorrect count on the last page |
2024-04-18 | LOOKUP-236 | App displays an incorrect backup count for a public and private lookup with the same name |
2024-03-28 | LOOKUP-224 | High volume of lookups and backups causes slow performance on the Health Overview dashboard |
2023-12-06 | LOOKUP-216, LOOKUP-185 | After editing a cell in a lookup file, the view returns to the first row instead of the last edited row |
2023-10-31 | LOOKUP-215 | _key with # doesn't work |
Version 4.0.1
Date filed | Issue number | Description |
---|---|---|
2023-08-17 | LOOKUP-193 | Some users can't view lookup files due to a special character in the usernameWorkaround:Edit the username and remove the special character, or create a new user with the same roles and capabilities |
2023-07-04 | LOOKUP-185, LOOKUP-216 | After editing a cell in a lookup file, the view returns to the first row instead of the last edited row |
2023-06-28 | LOOKUP-184 | Lookup editor doesn't support root_endpointWorkaround:Currently, the only workaround is to manually attach the {color:#ff5630}root_endpoint{color} in the URL if you face a *404* issue while navigating. |
Version 4.0.0
Date filed | Issue number | Description |
---|---|---|
2023-05-17 | LOOKUP-180 | Editing a cell in a lookup file with an ampersand character (&) produces "&" in the cell |
2023-04-06 | LOOKUP-167 | Copy and paste function broken for filling down columns, pasting from external sources, and copying multiple selected rows |
2023-03-30 | LOOKUP-163 | Pasting error returns only a single cell of content after copying multiple rows and columns |
2023-03-27 | LOOKUP-160 | Lookup editor sometimes fails to import CSV files and save backups after updating to 4.0Workaround:If the app fails to import CSV files and save backups, complete the following steps to troubleshoot:
These steps are valid for both on-premises and cloud users. |
2023-03-27 | LOOKUP-161 | "The lookup file could not be saved" error while saving a CSV lookup file containing special charactersWorkaround:The 4.0 version of the Splunk App for Lookup File Editing is no longer available in Splunkbase due to errors related to special characters in CSV files. If you already downloaded the 4.0 version of the app and you're experiencing errors, upgrade to the Splunk App for Lookup File Editing 4.0.1 when available or downgrade to version 3.6. |