Known issues

Publication date	Defect number	Description
2017-02-16	TAB-2291	When installing two add-ons with inputs that have the same name, the setup page for these add-ons might be mixed up.
2017-02-15	TAB-2284	Adding a setup parameter field and marking it as required does not result in a required field in the packaged add-on.
2017-02-15	TAB-2275	JSON path highlighting is slow for some expressions.
2017-02-14	TAB-2267	Running more than 10 add-ons in your development environment might negatively impact Add-on Builder's performance.
2017-02-12	TAB-2247	After deleting a data input or alert action, some setup configurations might not be updated.
2017-02-12	TAB-2245	After upgrading an add-on from 2.0.0, the add-on's Configuration page displays errors if any input or setup parameter has the same display label. To work around this issue, ensure that each parameter in your add-on has a unique label.
2017-01-23	TAB-2193	The setup page configurations are not kept in sync between an add-on project and the add-on on the development machine. This issue only affects add-ons in the development environment, not in production.
2017-01-23	TAB-2187	Performance issue: it takes more than 5 seconds to enter the Validate & Package page.
2017-01-22	TAB-2180	After upgrading Add-on Builder, an existing data input with custom Python code might not collect data without additional modification.
2017-01-21	TAB-2175	HTML is not displayed with beautified format.
2017-01-21	TAB-2172	Timestamp conversion result is fixed width. Padding 0 is added automatically.
2017-01-20	TAB-2169	Saving a data input but not clicking Finish might cause the data input to not work as expected.
2017-01-19	TAB-2164	Clicking Export multiple times quickly might result in a damaged package file.
2017-01-17	TAB-2162	Due to a limitation in Python 2.x, the time zone formats "%z" and "%Z" are not supported, and time_str2str() doesn't support converting epoch timestamps to time strings.
2017-01-20	TAB-2144	Modular data input does not work after renaming the add-on. To work around this issue, restart Splunk Enterprise after renaming the add-on.
2017-01-17	TAB-2134	When building a data input or creating a new add-on, an erroneous message is displayed, stating that you must restart Splunk Enterprise for changes to take effect. However, restarting is not required. To work around this issue, disregard this message.
2017-01-16	TAB-2133	During validation, add-ons fail the best practices rule Validate app certification due to features that were deprecated in Splunk Enterprise 6.5.
2017-01-16	TAB-2132	Add-on setup parameters that are in progress are not synchronized with the production setup page under Manage Apps.
2017-01-16	TAB-2131	The backslash character (\) and some translated characters do not work in filters. To work around this issue, escape these characters.
2017-01-16	TAB-2130	The dynamic deleting checker does not work as expected.
2017-01-16	TAB-2129	HTML tags are displayed in fields.
2017-01-16	TAB-2128	Searching with translated characters does not work as expected.
2017-01-16	TAB-2126	The Add button is not displayed when the browser width is small.
2017-01-16	TAB-2124	Modular input checkpoint highlighting does not work when the JSON response is an array.
2017-01-12	TAB-2100	Deleting an add-on or add-on project requires restarting Splunk Enterprise before reinstalling the add-on or importing the add-on project again.
2017-01-12	TAB-2097	Drag-and-drop components open a new tab to search the text in Firefox.
2017-01-11	TAB-2092	After creating a data input that uses checkpointing, the initial checkpoint value cannot be changed.
2017-01-10	TAB-2089	The JSON path for data inputs does not support @.length. To work around this issue, use [-1] instead.
2017-01-09	TAB-2087	Some events are missed while editing a REST data input.
2017-01-08	TAB-2073	After installing both Splunk Enterprise and Add-on Builder, opening the Add-on Builder directly results in the "Maximum call stack size exceeded" error. To work around this issue, go to the Splunk Enterprise home page first and close the data collection dialog box that is displayed.
2017-01-07	TAB-2069	After upgrading Add-on Builder, an error occurs when you try to edit the properties of an existing add-on or export it. To work around this issue, open the add-on in Add-on Builder by clicking it, which upgrades the add-on project, then try again.
2017-01-07	TAB-2061	The default line breaker for JSON files should be "Auto" rather than "Every Line".
2017-01-07	TAB-2059	Testing a shell command that doesn't end causes the test to never end.
2017-01-07	TAB-2057	An error message "internal error 500" is displayed when trying to import an add-on that was not created by Add-on Builder.
2017-01-06	TAB-2045	An error occurs when importing an add-on using Internet Explorer in Windows. To work around this issue, use a different web browser such as Chrome or Firefox.
2017-01-06	TAB-2043	An error occurs while trying to delete or rename an add-on because its data inputs are still running. To work around this issue, go to Configure Data Collection and disable the data inputs for the add-on first.
2017-01-06	TAB-2041	Input names that worked in the previous versions of Add-on Builder are invalid now. To work around this issue, rename the input according to the error message instructions.
2017-01-06	TAB-2034	Panels flash repeatedly while performing validation. To work around this issue, do not navigate to other pages until validation has finished.
2017-01-05	TAB-2014	An error message is displayed when trying to use a data input that was created using Python code for which single instance mode was enabled. To work around this issue, leave the collection interval blank for the data input.
2017-01-04	TAB-2009	The backslash character (\) and some translated characters do not work in filters. To work around this issue, escape these characters.
2017-01-04	TAB-2008	Some resources cannot be loaded under a reverse proxy.
2017-01-04	TAB-1999	The UI is not displayed correctly when radio button groups have several options.
2017-01-03	TAB-1998	Checkpoints are not deleted for data inputs that are deleted. To work around this issue, you can delete the checkpoint file manually.
2017-01-02	TAB-1981	Help text for field inputs exceeds the panel border.
2017-01-02	TAB-1978	Renaming a visible add-on creates an additional icon on the Splunk Enterprise home page.
2016-12-27	TAB-1934	When creating a data input using checkpointing, in some cases the output panel might highlight more fields than the ones that you specified.
2016-12-27	TAB-1926	When testing a REST data input that you are creating, the value of a setup parameter is not correctly used for testing. This error might occur when not using namespaces where needed, or when using proxy or logging settings directly rather than using the value of global variable.
2016-12-27	TAB-1925	When creating an add-on that is visible, the Splunk Enterprise home page does not display the icon until after restarting.
2016-12-26	TAB-1903	An unnecessary [default] stanza is created in tags.conf for the first add-on that is created, causing the add-on to fail app certification. To work around this issue, manually delete the empty [default] stanza from the add-on's tags.conf file.
2016-12-21	TAB-1866	Add-on Builder does not load the source type when editing CIM mapping for an existing add-on.
2016-12-20	TAB-1854	If an add-on is deleted from the file system rather than from the Add-on Builder UI, Add-on Builder cannot remove associated components such as data inputs.
2016-12-20	TAB-1849	Add-on errors are displayed in the console when opening the Search & Reporting app.
2016-12-15	TAB-1817	UI display errors sometimes occur when dragging inputs from the Component Library to the center panel and back to the Component Library.
2016-12-13	TAB-1798	App Pre-Certification validation reports erroneous failures for add-ons, specifically errors mentioning missing itsi*.conf or deep_dive_drilldowns.conf files.
2016-11-29	TAB-1736	You cannot install Splunk DB Connect on the same instance as Add-on Builder. Conflicts occur with Python libraries when installing Add-on Builder with other apps.
2016-11-08	TAB-1631	The Download Package button is grayed out on the Validate & Package page. This issue occurs when you place a file in your add-on directory to which you do not have sufficient access permission.
2016-10-26	TAB-1589	The preview when uploading sample data is not correct. When you upload sample CSV, PSV, or TSV files, the events that are displayed for preview might not be the same events that are indexed.
2016-10-12	TAB-1545	Alert action doesn't write events correctly without the CIM add-on installed.
2016-10-12	TAB-1543	Modular inputs do not pass App Certification.
2016-10-12	TAB-1502	The sourcetype and eventtype defined in an alert action is not managed by Add-on Builder, which might cause conflicts in some rare cases.
2016-10-12	TAB-1500	Could not open multiple add-ons in multiple tabs.
2016-10-12	TAB-1438	The Add-on Setup Parameters tab is not displayed in Splunk Enterprise 6.4.
2016-10-12	TAB-1388	In Create Alert Actions, the helper.writeevents function does not clean up added events.
2016-10-12	TAB-1374	Field validation failure prevents the Create Alert Action wizard from going to the next page.
2016-10-12	TAB-1371	Indicator numbers and bar charts are designed to grow dynamically in Validation.
2016-10-12	TAB-1355	HTTP 500 error occurs when testing a shell command input with Splunk Enterprise installed in Windows.
2016-10-12	TAB-1330	Some lookups are referred to by prebuilt panels or saved searches rather than transforms.conf.
2016-10-12	TAB-1263	The Best Practice check for duplicated stanza headers or fields will pass even if duplication exists.
2016-10-12	TAB-1257	To access one of multiple user accounts on a setup page, you still needs to manually add a option in inputs/alerts to refer to one of the accounts.
2016-10-12	TAB-1235	Percentage of "Validation Status" is not accurate.
2016-08-16	TAB-1152	Field extraction hangs at 80% for some samples when the raw event size is very large or there are too many (100+) groups after clustering.