Known issues

The following are known issues in the Splunk App for Lookup File Editing version 3.6.0. If no known issues are listed, no issues have been reported.

Date filed	Issue number	Description
2023-05-17	LOOKUP-180	Editing a cell in a lookup file with an ampersand character (&) produces "&amp" in the cell
2023-04-24	LOOKUP-178	Replicate=false is not working as expected
2023-02-14	LOOKUP-118	Splunk App for Lookup File Editing is not able to manage KV store entries using type enforcement
2023-01-13	LOOKUP-104	Lookup File Editor-3.6.0 - Unable to update file which contain ":" in file name
2023-01-02	LOOKUP-98	Lookup File Editor-3.6.0 - Unable to save lookup after drag column
2022-11-30	LOOKUP-77	Fields with epoch times are not correctly parsed within the Lookup File Editor
2022-11-30	LOOKUP-76	Can not scroll through lookups wit more than 100 Rows - Lookup File Editor 3.6.0
2022-11-20	LOOKUP-74	Lookup Editor App facing performance issues after Splunk Upgrade to version 9.0.0
2022-11-14	LOOKUP-73	Lookup editor don't allow the option 'bool'
2022-10-13	LOOKUP-71	Lookup Editor App v3.6.0 on Splunk Cloud v8.1.2101.2 only loads a blank page in the Lookups tab
2022-09-09	LOOKUP-69	Lookup Editor adds extra whitespace to last column if imported file has newline in one cell
2022-08-19	LOOKUP-67	Cannot upload large csv file to lookup editor app
2022-08-08	LOOKUP-63	Kvstore looup issue for Splunk App for Lookup File Editing
2022-07-21	LOOKUP-61	Lookup editor not functioning after upgrading Splunk to 8.2.x
2022-06-08	LOOKUP-56	Lookup backups filling up disk space and not being removed automatically after some time - no method to manage it by the customer
2022-04-18	LOOKUP-44	Import not working correctly when data has ; characters Workaround: Best workaround is as follows: - navigate on splunkweb to Settings -> KNOWLEDGE -> Lookups. - then choose "Add new" under "Lookup table files". - fill in the relevant fields and then upload the file of interest. - change the lookup scope to app or/system as/if needed. - change lookup permission as/if needed. - finally go back to the Lookup Editor and look up the newly imported lookup file: the delimiters will be correct, despite the presence of the invalid character in the field values (for upload purposes). Original suggestion* Please ensure the CSV file is only using one of the following delimiters and that the CSV does not include other delimiters as field values: comma (","), semicolon (";"), tabspace ("\t"), pipe ("|"), or carrot ("^"). Afterwards you can import the csv file directly from the Lookup Editor.