List of Supported Translatable Fields

The following list contains all translatable fields supported in NetSuite.

It was compiled to provide specific information about translatable fields whose behavior may vary across NetSuite features.

Translatable Field; Translatable Field ID	Usage — Leads to View	Usage — Should lead to GROUP	Known to create duplicate IDs unless the Best Practices are observed	Lockable in Bundler	Lockable in Manage Translations	Notes	Owner
ENTRY_FORM_TEMPLATE_NAME ENTRY_FORM_TEMPLATE_FIELD_GROUP_LABEL ENTRY_FORM_TEMPLATE_SECTION_LABEL ENTRY_FORM_TEMPLATE_MACHINE_LABEL ENTRY_FORM_TEMPLATE_FIELD_LABEL	ENTRY_FORM_TEMPLATE ENTRY_FORM_TEMPLATE_FIELD_GROUP ENTRY_FORM_TEMPLATE_SECTION ENTRY_FORM_TEMPLATE_MACHINE ENTRY_FORM_TEMPLATE_FIELD	ENTRY_FORM_TEMPLATE	NO	YES	Most fields are lockable.	When you create an entry form, the following translatable fields that are not lockable are also created: 16,AllCustomField,Descr 17,AllCustomField,FieldHeld 43, 44	SUITEBUILDER
FORM_TEMPLATE_NAME FORM_TEMPLATE_FIELD_GROUP_LABEL FORM_TEMPLATE_TAB_LABEL FORM_TEMPLATE_MACHINE_LABEL FORM_TEMPLATE_FIELD_LABEL FORM_TEMPLATE_SUM_FIELD_LABEL FORM_TEMPLATE_VIEW_LABEL	FORM_TEMPLATE FORM_TEMPLATE_FIELD_GROUP FORM_TEMPLATE_TAB FORM_TEMPLATE_MACHINE FORM_TEMPLATE_FIELD FORM_TEMPLATE_SUM_FIELD FORM_TEMPLATE_VIEW	FORM_TEMPLATE	NO	YES	Most fields are lockable.	When you create a form template, the following translatable fields that are not lockable are also created: 16,AllCustomField,Descr 17,AllCustomField,FieldHeld 43, 44	SUITEBUILDER
SAVE_DASHBOARD_NAME; 55 SAVE_DASHBOARD_NOTES; 56	SAVE_DASHBOARD	SAVE_DASHBOARD	NO	These fields are not lockable even on Bundle level.	These fields are not lockable even on Bundle level.	—	UI
KPI_REPORT_NAME KPI_REPORT_DESCRIPTION KPI_REPORT_KPI_LABEL KPI_REPORT_DATE_RANGE_LABEL	KPI_REPORT KPI_REPORT_KPI KPI_REPORT_DATE_RANGE	KPI_REPORT	YES	These fields are not lockable even on Bundle level.	These fields are not lockable even on Bundle level.	—	UI
TRANSLATION_COLLECTION_NAME TRANSLATION_COLLECTION_DESCRIPTION	TRANSLATION_COLLECTION	TRANSLATION_COLLECTION	NO	YES	YES	—	INTERNATIONALIZATION
WORKFLOW_NAME WORKFLOW_STATE_NAME WORKFLOW_ACTION_DISPLAY_LABEL WORKFLOW_ACTION_MESSAGE_TEXT WORKFLOW_ACTION_ERROR_TEXT WORKFLOW_ACTION_BUTTON_TEXT	WORKFLOW WORKFLOW_STATE WORKFLOW_ACTION	WORKFLOW	NO	YES	Most fields are lockable.	When you create one of these translatable fields, the following translatable field that cannot be locked is also created: 'CUSTOM FIELD LABEL' type (TF 16, 17)	SUITEFLOW
CENTER_TYPE_DESCRIPTION; 15	CUSTOM_CENTER	CENTER	NO	This field is not lockable even on Bundle level.	This field is not lockable even on Bundle level.	—	SUITEBUILDER
CENTER_CATEGORY_LABEL; 45	CENTER_CATEGORY	—	YES	This field is not lockable even on Bundle level.	This field is not lockable even on Bundle level.	—	SUITEBUILDER
CENTER_TAB_NAME; 51	CENTER_TAB	—	NO	This field is not lockable even on Bundle level.	This field is not lockable even on Bundle level.	—	SUITEBUILDER
CUSTOM_FIELD_LABEL CUSTOM_FIELD_HELP	CUSTOM_FIELD	FORMS, WORKFLOW, RECORD, ... dependent on stype	NO	YES	NO	—	SUITEBUILDER
CUSTOM_RECORD_NAME; 18 CUSTOM_LIST_NAME; 18	CUSTOM_RECORD	—	NO	Most fields are lockable, it depends on specific cases.	NO	—	SUITEBUILDER
CUSTOM_RECORD_SUBTAB; 10 CUSTOM_SUBTAB_TITLE; 10	CUSTOM_FIELD_TAB	—	NO	These fields are not lockable even on Bundle level.	These fields are not lockable even on Bundle level.	—	SUITEBUILDER
CUSTOM_SUBLIST_DESCRIPTION; 9 CUSTOM_SUBLIST_LABEL; 9	CUSTOM_SUBLIST	?CUSTOM RECORD	NO	These fields are not lockable even on Bundle level.	These fields are not lockable even on Bundle level.	—	SUITEBUILDER
CUSTOM_TRANSACTION_NAME; 23	CUSTOM_TRANSACTION	CUSTOM_TRANSACTION	NO	YES	YES	—	SUITEBUILDER
CUSTOM_TRANSACTION_STATUS_DESCRIPTION; 24	CUSTOM_TRANSACTION_STATUS	CUSTOM_TRANSACTION	NO	YES	YES	—	SUITEBUILDER
CUSTOM_SEGMENT_LABEL CUSTOM_SEGMENT_HELP	CUSTOM_SEGMENT	CUSTOM_SEGMENT	Cannot be determined, the behavior is not finished on the owner’s side.	YES	Most fields are lockable.	When you create one of these translatable fields, the following translatable fields that cannot be locked are also created: 19 AllCustomRecordEntry Name 20 AllCustomRecordEntry RawFullName 48 AllFormTemplateField Label 43 AllTask Label 44 AllTask ShortName	SUITEBUILDER
CUSTOM_RECORD_ENTRY_NAME CUSTOM_LIST_VALUE (lead to CUSTOM_RECORD_ENTRY)	CUSTOM_RECORD_ENTRY	—	NO	NO	NO	—	SUITEBUILDER
SAVED_CSV_NAME SAVED_CSV_DESCRIPTION (leads to SAVED_CSV_IMPORT)	SAVED_CSV_IMPORT	SAVED_CSV_IMPORT	NO	NO	NO	—	INTEGRATION
SAVED_SEARCH_NAME; 37	SAVED_SEARCH	SAVED_SEARCH	NO	YES	YES	—	SA:CORE
SAVED_SEARCH_HIGHLIGHT_DESCR	SAVED_SEARCH_HIGHLIGHT	SAVED_SEARCH	YES	YES	YES	—	SA:CORE
SAVED_SEARCH_COLUMN_LABEL	SAVED_SEARCH_COLUMN	SAVED_SEARCH	YES	YES	YES	—	SA:CORE
SAVED_SEARCH_COLUMN_DETAIL_LABEL SAVED_SEARCH_COLUMN_DETAIL_SUMMARY_LABEL	SAVED_SEARCH_COLUMN	SAVED_SEARCH	YES	YES	YES	—	SA:CORE
SAVED_SEARCH_SUMMARY_LABEL	SAVED_SEARCH_COLUMN	SAVED_SEARCH	YES	YES	YES	—	SA:CORE
SAVED_SEARCH_FIELD_LABEL	SAVED_SEARCH_FIELD	SAVED_SEARCH	YES	YES	YES	—	SA:CORE
SCRIPT_RECORD_ACTIONLABEL; 57	SCRIPT_RECORD	—	NO	NO	NO	Internal issues with lockability	RECORD ARCHITECTURE: CORE; SUITESCRIPT
SCRIPT_NAME; 100 SCRIPT_DESCRIPTION; 101	SCRIPT	SCRIPT	NO	YES	YES	—	SUITESCRIPT
SCRIPT_BUTTON_LABEL; 5	SCRIPT_BUTTON	SCRIPT	YES	YES	YES	—	SUITESCRIPT
CUSTOM_RECORD_LINK; 42 TASK_LINK_LABEL; 42	CUSTOM_LINK TASK_LINK	CUSTOM_RECORD instance	YES	Depends on the type of usage	NO	This translatable field is often created as a by-product during creation of other translatable fields.	—
DATASET_DESCRIPTION DATASET_FIELD DATASET_FORMULA DATASET_NAME	DATASET, but now: UsrStrTran	DATASET INSTANCE	A collection is automatically generated when strings with these translatable fields are exported, therefore the duplicate ID issue cannot occur with them.	These fields are not lockable even on Bundle level.	These fields are not lockable even on Bundle level.	—	SUITEANALYTICS
REPORT_NAME REPORT_ROW_AXIS REPORT_COLUMN_AXIS REPORT_MEASURE	REPORT, but now: UsrStrTran	REPORT INSTANCE	A collection is automatically generated when strings with these translatable fields are exported, therefore the duplicate ID issue cannot occur with them.	These fields are not lockable even on Bundle level.	These fields are not lockable even on Bundle level.	—	SUITEANALYTICS
CHART_NAME CHART_TITLE CHART_SUBTITLE CHART_CATEGORY_AXIS CHART_CATEGORY_ITEM CHART_LEGEND_AXIS CHART_LEGEND_ITEM CHART_MEASURE	CHART, but now: UsrStrTran	CHART INSTANCE	A collection is automatically generated when strings with these translatable fields are exported, therefore the duplicate ID issue cannot occur with them.	These fields are not lockable even on Bundle level.	These fields are not lockable even on Bundle level.	—	SUITEANALYTICS
WORKBOOK_DESCRIPTION WORKBOOK_NAME	WORKBOOK, but now: UsrStrTran	WORKBOOK BASE	A collection is automatically generated when strings with these translatable fields are exported, therefore the duplicate ID issue cannot occur with them.	These fields are not lockable even on Bundle level.	These fields are not lockable even on Bundle level.	—	SUITEANALYTICS
TABLEVIEW_FIELD TABLEVIEW_NAME	DATAVIEW, but now: UsrStrTran	DATAVIEW INSTANCE	A collection is automatically generated when strings with these translatable fields are exported, therefore the duplicate ID issue cannot occur with them.	These fields are not lockable even on Bundle level.	These fields are not lockable even on Bundle level.	—	SUITEANALYTICS

For more information about the proper import and export process, see Best Practice for Exporting and Importing Strings From Translatable Fields.

Related Topics:

Manage Translations UI Overview

Translation Statistics

Manage Translations Page Collections Subtab

Manage Translations Page Import Jobs Subtab

Translatability Support

Globalization Glossary

Best Practice for Exporting and Importing Strings From Translatable Fields

General Notices