NetSuite User Interface

Project Addresses

With Advanced Projects (a Project Management feature) disabled, NetSuite does not automatically copy address sub-records down from the customer to new projects. The Field Service scripts will handle this process in this scenario. Custom fields on the address sub-record will not be copied by the Field Service scripts, only the basic NetSuite address fields.

Field Service Asset – Address Text and Address Select

Each time the Field Service Asset record is saved, the value stored in the Address Text field will be replaced with the address selected in the Address Select field. Changes to the Address Text field will not be retained unless the Address Select field is first cleared.

Field Service Asset – Sourcing of Longitude and Latitude

If a value already exists in the Latitude field of the Field Service asset record, changes to the Address Text field will not source new values into the Longitude and Latitude fields. If you want new values to be sourced into these fields you must first clear out any existing values.

Field Service Asset – Uniqueness Tests

Any fields used as part of an asset uniqueness test (set up within the "uniqueTemplate"), must also be accessible as elements within "views/itemfulfillment/assets", if you are creating assets automatically from item fulfillment.

Each element setup under "views/itemfulfillment/assets" that is used within the "uniqueTemplate" must also have a value set in it’s "sourcefrom" property, even if this value is empty (for example, "sourcefrom": "|").

Longitude and Latitude Data and the Geolocation Scheduled Script

The Field Service Geo scheduled script deployment is not responsible for initially populating the Field Service Longitude and Field Service Latitude fields. Instead, when text is entered into the Field Service Address field, its value is immediately used to find the correct longitude and latitude to populate the longitude and latitude fields.

Default Forms on Recurring Cases and Tasks

When recurring cases or task instances are created by the system, they will be set to use the preferred custom form for the corresponding record. Currently there is no way to configure a different custom form to be used when recurring case or task instances are created.

Copying Recurring Tasks

Using NetSuite’s Copy feature to create new task records when those tasks are related to a recurrence schedule is not recommended and will likely result in unexpected behavior.

Service Reports and Images

For NetSuite’s PDF generator to access images from the file cabinet it must be provided secure access by a temporary API key. The key provided by Field Service Management expires after 60 seconds. If the PDF has not finished being generated before this key expires, images will no longer be available and will not appear on the resulting PDF.

Closing Cases Using the NetSuite Interface

When a case is closed using the Field Service scripts, certain steps are taken automatically by the Field Service scripts (Field Service End Date is populated and various automations are triggered such recalculation of Unbilled Amounts). If a user manually changes the case status through the NetSuite UI, they will also need to manually perform the steps that would otherwise have been automated by the Field Service scripts.

PM Programs – Max Record Limit

When using the Program feature set to automatically create Case records underneath a Project record there is an undocumented 1000 case limit.

If the number of Program cases under a single project exceeds 1000 records you will experience unexpected behaviors involving automatic creation of many duplicate case records.

If a single PM Program is likely to approach this 1000 record limit, it should be closed down and a new PM Program should be created to continue the series.