​
Introduction

Cloudpress allows you to set additional field values when exporting content from Google Docs by using something we refer to as a property table. This property table allows you to specify additional properties for the document that are then mapped to fields in your Content Management System (CMS).

​
Requirements

This property table has a few requirements:

  1. The property table must be at the top of the Google Doc before any other content.
  2. The property table must have exactly two columns.
  3. The first column will be the name of the property and must match the name of a field in your CMS.
  4. The second column will contain the property’s value and must contain a single line of text or image.

​
Configuring Cloudpress to use the property table

Configuring Cloudpress to use the property table depends on whether you are exporting content with the Add-on, or the Export Content page.

​
Allowed property names

The property name must match the name of an available field in your underlying CMS. The available fields will differ between the various CMSs. For a CMS such as WordPress, a fixed number of allowed field names are available.

A CMS such as Webflow enables you to define custom fields, and the field names will therefore depend on your implementation. You can refer to the relevant section for each of the CMSs listed below for more information.

​
Allowed property values

As mentioned earlier, the value of a property must be one of the following:

  1. A single line of text
  2. A single image

If the underlying field is an image - such as the featured_image field in WordPress, the value must be an image, as in the example screenshot at the top of this page. All other field values must be specified as a text value, and Cloudpress will try its best to convert that to the correct value for the field.

In cases where the field can accept a list of items, such as the categories field in WordPress, you can delimit items with a semi-colon (;). Once again, you can refer to the screenshot at the top of this page for an example.

​
Errors when setting field values

If Cloudpress cannot set a field value, it will still export the document, but it will indicate that the export job has warnings. You will see a warning label on the Job History page.

Clicking on the job will take you to the Job Detail page, where you can refer to the Log for more information about the warnings.

​
Wrong field name

If the property name does not match a field in your CMS, Cloudpress will give the following warning:

Field '<fieldname>' was not found

The resolve this problem, make sure that the property name matches a field in your CMS. You can refer to the documentation for your CMS in the Integrations section of the documentation for more information.

​
Wrong field type

If the value you specified in the property value column is incompatible with the type of field in your CMS, Cloudpress will give the following warning:

The value supplied for the '<fieldname>' field is incompatible with the field type

This can happen, for example, when the field is expecting text, but you specify an image in the property value column. The resolve this problem, make sure that the value you supply is compatible with the type of field in your CMS.

You can refer to the documentation for your CMS in the Integrations section of the documentation for more information.

​
Wrong lookup value

When the field you are trying to update in your CMS is a lookup field, and the value you specified does not exist, Cloudpress will give the following warning:

The value '<value>' supplied for the field '<fieldname>' is invalid. <explanation>.

The screenshot below gives an example of this. In this case, the user tried to set the value for the categories field in WordPress, but no category with the name or ID “Category 3” exists. Cloudpress try and give an explanation for the error and how to fix it. In the screenshot below, Cloudpress states that the value must match the ID or title of an existing category in WordPress.

You can refer to the documentation for your CMS in the Integrations section of the documentation for more information.