CMS Page Import
The CMS Page Import lets you add or update website pages by importing them from a CSV file. This is useful when you have a large number of pages to create or edit. The import is also an important tool when you want to export pages from one account and import them into another account, for example, from your sandbox account to your production account.
Unlike pages that you create or edit with Site Management Tools, pages you create or update by CSV Import are automatically placed in a published state and are visible based on the visibility start and end dates for the page record.
For information about working with this record in the UI, see CMS Page Record.
If you are importing pages and do not want them to be immediately visible to site visitors, be sure to give the pages future start date.
For details about fields that can be mapped in the CMS page record, see the SOAP Schema Browser’s CMS page reference page. You can use the field definitions here as a basis for creating your own CSV import template file. For information about working with the SOAP Schema Browser, see SOAP Schema Browser.
CMS Page Record Fields
The following table lists the fields that are available for import or update for CMS Pages. Required fields are marked with an asterisk.
|
Addition To |
The value specified here populates the addition to head field on the CMS Page record. This is used to add code such as Java Script, HTML, or CSS to the head area of the page. |
|
CMS Page Type* |
This value specifies the CMS Page Type and links to the Name field on the CMS Page Type record. |
|
Custom Record Data |
If you added custom fields to pages of this type, this field lets you specify the instances of the custom record data assigned to the page type record. |
|
Custom Record External ID |
This is a user-defined mapping field that can be used for linking to page types when the import data originated as an export from a different account. |
|
End Date |
This value identifies the date and time that the record should expire. If you omit this date from the import file or leave the value blank, no end date is assigned, meaning the page never expires. When including a date and time in the field, use the format specified by the preferences in your NetSuite account. |
|
External ID |
The External ID might originate with data that is exported from a third party system or it can be user-defined and added to the CSV file. The external ID must be unique for each record and can be used as a primary key for updating records with CSV Import. |
|
Internal ID |
The Internal ID is a primary key assigned to a CMS Page record when it is created in the system. When performing an import that creates new CMS Page records, the Internal ID is not included in the import and is automatically assigned when the records are created. For existing CMS Page records, you can use the Internal ID as the primary key when performing a CSV Import to update existing pages. You can create a saved search to generate a listing of pages and their internal IDs. |
|
Meta Description |
The value entered in this field populates the Meta Description field on the CMS Page record and is set as the value of the content attribute for the meta description HTML element for the page. |
|
Meta Keywords |
The value entered in this field populates the Meta Keywords field on the CMS page record and is set as the value of the content attribute for the meta keywords HTML element for the page. |
|
Name |
This value specifies the page name. |
|
Page Heading |
This value populates the Page Heading field on the CMS Page record. If the page template file supports it, the heading is displayed to site visitors. |
|
Page Title |
This identifies the page title and populates the HTML <title> element on the page. This is usually the title of the page that is shown in the tab or browser title bar. |
|
Site* |
This value identifies the website. You can use the numeric site id or the site name during the import. Be sure to edit the field mapping to specify if the value in your CSV file is the internal ID or the site name. You cannot use both name and site ID in a single import file. |
|
Start Date |
This value identifies the date and time the page should begin displaying on the site. If you omit the start date from the file or leave the value blank, no start date is assigned, and the page displays immediately. When including a date and time in the field, use the format specified by the preferences in your NetSuite account. |
|
Template* |
Specifies the template for the page. If the page uses the default template, leave the field empty or enter default to use the default template. If the page uses a custom template, enter the template name. |
|
Type* |
Specifies the type of page. Valid entries are:
|
|
URL |
This field specifies the page URL. |
|
CMS Page Tags |
The tags field lets you specify tags for the CMS Page Record. See CMS Page Tags Sublist. |
CMS Page Tags Sublist
When you include tags in the CSV import for CMS Pages, the CSV file must have a separate tag column for each tag. For example, if each record in the CSV file contains only one tag for each page, then you need only one tag column, but if one or more pages has multiple tags, then the file must include multiple tag columns. In the following sample CSV file you see four separate tag columns. Some records have multiple tags, with four tags being the most, and other records have only one tag
|
Name |
... |
Tag1 |
Tag2 |
Tag3 |
Tag4 |
|
About Us |
... |
About Us |
Company Information |
— |
— |
|
Back To School |
... |
Sale |
School Supplies |
Back to School |
Fall |
|
Locations |
... |
Store Locations |
— |
— |
— |
|
Return Policy |
... |
Return Policy |
— |
— |
— |
By default, the NetSuite Fields mapping for CMS Page Tags includes only one column. You can add more tag columns to the import by clicking the Add New tag button. The following example illustrates four tag columns to accommodate four tag columns in the CSV file:
You can then map each tag column in the CSV file to a CMS Page Tags column in the import.
CMS Page Translation Sublist
CMS pages support the translation locale’s supported by NetSuite. The following table lists the fields required for importing commerce category translations by CSV. Enter the values in the language specified by the value you enter in the Locale field.
|
External ID |
The external ID for the landing page for these translation values. |
|
Addition To |
JavaScript, HTML, or other code to include in the <head> area of the commerce category page when it is rendered on the site. |
|
Locale |
Specify the locale code for this translation subsublist. See Locale Code Reference for valid codes. |
|
Meta Description |
This is for SEO data you provide to enter for your translations. |
|
Meta Keywords |
This is for SEO data you provide to enter for your translations. |
|
Page Heading |
The page heading to display on the landing page for the specified language. |
|
Page Title |
The title of the page. This populates the HTML <title> element. |
By default, the field mapping for translations includes column sets for only one language. You can click the +button to add another set of columns for additional languages. Your CSV file must include the translation values for different languages in different column sets. To help organize the import, consider prefixing the column names with the locale code as in the following example:
-
es_ES_External-ID
-
es_ES_Addition-To
-
es-ES_Locale
-
es_ES_Meta Description
-
es_ES_Meta Keywords
-
es_ES_Page Heading
-
es_ES_Page Title
-
fr_FR_External-ID
-
fr_FR_Addition-To
-
fr_FR_Locale
-
fr_FR_Meta Description
-
fr_FR_Meta Keywords
-
fr_FR_Page Heading
-
fr_FR_Page Title
Locale Code Reference
When you import translations for commerce category you must specify the locale Code for the translation.
|
Locale Code |
Language |
|
af_ZA |
Afrikaans |
|
sq_AL |
Albanian |
|
ar |
Arabic |
|
hy_AM |
Armenian |
|
ms_MY |
Bahasa Malai |
|
bn_BD |
Bengali |
|
bs_BA |
Bosnian |
|
bg_BG |
Bulgarian |
|
zh_CN |
Chinese (Simplified) |
|
zh_TW |
Chinese (Traditional) |
|
hr_HR |
Croatian |
|
cs_CZ |
Czech |
|
da_DK |
Danish |
|
nl_NL |
Dutch |
|
en_AU |
English (AU) |
|
en_CA |
English (CA) |
|
en |
English (International) |
|
en_GB |
English (UK) |
|
et_EE |
Estonian |
|
tl_PH |
Filipino |
|
fi_FI |
Finnish |
|
fr_CA |
French (Canada) |
|
fr_FR |
French (France) |
|
de_DE |
German |
|
el_GR |
Greek |
|
gu_IN |
Gujarati |
|
he_IL |
Hebrew |
|
hi_IN |
Hindi |
|
hu_HU |
Hungarian |
|
is_IS |
Icelandic |
|
id_ID |
Indonesian |
|
it_IT |
Italian |
|
ja_JP |
Japanese |
|
kn_IN |
Kannada |
|
ko_KR |
Korean |
|
es_AR |
Latin American Spanish |
|
lv_LV |
Latvian |
|
lt_LT |
Lithuanian |
|
lb_LU |
Luxembourgish |
|
mr_IN |
Marathi |
|
no_NO |
Norwegian |
|
fa_IR |
Persian (Iran) |
|
pl_PL |
Polish |
|
pt_BR |
Portuguese (Brazil) |
|
pt_PT |
Portuguese (Portugal) |
|
pa_IN |
Punjabi |
|
ro_RO |
Romanian |
|
ru_RU |
Russian |
|
sh_RS |
Serbian (Cyrillic) |
|
sr_RS |
Serbian (Latin) |
|
sk_SK |
Slovak |
|
sl_SI |
Slovenian |
|
es_ES |
Spanish |
|
sv_SE |
Swedish |
|
ta_IN |
Tamil |
|
te_IN |
Telugu |
|
th_TH |
Thai |
|
tr_TR |
Turkish |
|
uk_UA |
Ukrainian |
|
vi_VN |
Vietnamese |