Theme Metadata

Documentation article about Theme Metadata

·1 min read·View Oracle Docs

Theme Metadata

Theme Metadata

The first entries in the manifest file include metadata about the theme or extension itself. These fields are automatically populated when you initially run the gulp theme:deploy command.

json
1{
2 "name": "StandardTheme",
3 "vendor": "SuiteCommerce",
4 "type": "theme",
5 "target": "SuiteCommerce",
6 "version": "1.2.0",
7 "description": "Standard theme for SuiteCommerce",
8//...
  • Name (string) - uniquely identifies the name of the theme. This field is required.

  • Vendor (string) - identifies the vendor as a string. This field is required.

  • Type (string) - indicates if the type is a theme. This field is required.

  • Target (comma-separated string) - indicates the Commerce applications supported by the theme. This field is required.

  • Version (string) - indicates the version of the theme, such as 1.0.0. This field is required.

  • Description (string) - provides a description of the theme as it appears in NetSuite. This field is optional.

Frequently Asked Questions (4)

How is the theme metadata populated in NetSuite?
The theme metadata is automatically populated when you initially run the `gulp theme:deploy` command.
Are there any required fields in the theme metadata manifest?
Yes, the fields 'name', 'vendor', 'type', 'target', and 'version' are required fields in the theme metadata manifest.
Can the description field be omitted in the theme metadata?
Yes, the 'description' field is optional and can be omitted in the theme metadata.
What does the 'target' field in the theme metadata signify?
The 'target' field indicates the Commerce applications supported by the theme and is a required entry.
Source: Theme Metadata Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in General

View all General articles →