This document covers high level release notes and update instructions (when needed) intended for NetSuite administrators planning to update to a newer version of the the FieldAware For NetSuite (FA4NS) SuiteApp (bundle). Only changes to existing or important new functionality are recorded here.

Upgrading the FA4NS SuiteApp is, generally speaking, a straightforward process that rarely requires special care. From time to time update instructions are provided that need to be observed for the installation to work as intended. Please perform the steps in order provided. If you have any questions or corrections to these procedures please feel free to reach out to us, we’d be glad to hear from you and to improve this document.

Adds a flag to the item payload when the item is tracked for inventory in Netsuite.

Adds a "Completed" custom field on Sales Order line items to be set when the service item corresponding to the Job's task is completed. Additionally for customers with Parts Consumption enabled, it will also mark items completed in FieldAware.

Items and Employees synced to FieldAware that are now set inactive in NetSuite will also archive their FieldAware counterparts. Setting the NetSuite record back to active will unarchive the respective FieldAware record.

Fixed an issue that prevented synced NetSuite customers from setting their respective FA customer on hold when inactivated.

Allows simultaneous usage of the Bulk Sync Project Tasks functionality on different projects by one or multiple users when multiple script executions can be scheduled.

Choose whether you want the new “Completed” Sales Order Line Item field to show up in the respective forms.

Adds “scheduled job” duration field (in minutes) on the SO and FieldAware Job Custom Record and a “pause reason” field on Worked Hours Custom Record.

Adds a human friendly calculated scheduled job duration and planned effort field on the SO that show long durations in days/hours/minutes, ie. “2d 3h 42m”.

Adds a new parameter on the Attachments Suitelet that when enabled allows attachments to be viewed via external links. Such access was previously not allowed and displayed a json error.

Choose whether you want the new Scheduled Duration / Planned Effort fields displayed on the forms. You might want to display the calculated fields and hide the numeric fields.

If you would like attachments to be viewed from external, unauthenticated links, update the FieldAware Attachment Suitelet script deployment to enable “available without login”, set “execute as role” to a role that allows access to files and enable the “allow public access to attachments” parameter. You could then substitute the internal for an external link when needed (i.e. on an email template sent to customers) or permanently by making a request to our support team providing the external URL.

Adds support for FieldAware Parts Consumption. If this FieldAware feature is enabled, Planned and Used Quantity fields on the Sales Order line items are syncing their values from FieldAware and NetSuite item quantity is updated accordingly.

“Asset Manufacturing Guidelines” and “Asset Description” fields are increased to Text Area to better match FieldAware field size.

Fields on the FieldAware Job Custom Record sourcing from the “Attached PT” field now correctly source when the FieldAware Job is immediately created as a result of creating a new syncable Project Task.

The “Select Customer Address” field now displays synced customer addresses sorted alphabetically.

Phone numbers retain formatting when transmitted to FieldAware.

A validation message is displayed when saving a FieldAware Asset record without address.

Other smaller usability fixes.

Update deployments for the FieldAware Record Validation script to add the new validation on the FieldAware Asset record.

Internal engineering update.

Internal engineering update.

Fixes a regression introduced in 2.24.0 where a Project Task validation was incorrectly triggered on editing already synced PTs.

Allows a workaround to providing user permissions for Bulk Syncing of relevant Project Tasks of a Project.

If providing the necessary permissions to schedule the Map/Reduce bulk syncing script is not desirable, then change the execution role of SuiteLet “FieldAware PT Bulk Sync Schedule-SL” to a role that provides the permissions Setup → SuiteScripts (View) and Setup → SuiteScript Scheduling (Full).

Support for Project Templates and Bulk Syncing of relevant Project Tasks of a Project.

The FieldAware Job Type for a FieldAware Job created from a Project Task can now be selected.

To support Project Templates, previously non persistent FieldAware related fields on the Project Task are now changed to retain (persist) their value after save. These fields continue to source from Project defaults if their value during record load is empty but will now save the (sourced or user selected) value on save.

Select to show FieldAware Job Type on relevant Project Task forms if interested in using this feature.

Add these permissions to users/roles that need to schedule the bulk syncing of Project Tasks.

Workarounds for bugs and breaking changes when selecting addresses using the “New Project UI” introduced in NetSuite’s 2021.2 release.

UX improvements for customers with FieldAware Enterprise Model.

Adds syncing of FIeldAware’s Job “Planned Effort” field on the Sales Order and FieldAware Job Custom Record (JCR). This is a FA->NS sync only as the field is readonly in FieldAware.

Please make sure the two new Custom Fields are added to any relevant forms of SOs and JCRs.

Adds support for FIeldAware’s Enterprise Model.

If the FieldAware business is not on Enterprise Model then there’s nothing to do.

Otherwise, show the following custom fields on forms:

Fixes a situation present only in SuiteApp versions 2.20.0 and 2.21.0, under which a SuiteScript error could occur when a new customer (not previously saved) was first saved and at the same time set to sync to FieldAware.

Supports syncing Project Tasks with Planned Work feature enabled in the Company settings.

Added GPS location Lat/Long custom fields on NetSuite Address records that sync to the respective FieldAware location fields. Additionally, the Address country field and the “Is default billing” and “Is residential” Customer AddressBook checkbox fields are now synced to FieldAware locations.

Editing a syncable field of the AddressBook sublist (i.e. the address label) will now cause a sync of that address to FieldAware. Previously only edits of the actual address record would cause a sync.

Select to show the Address Lat/Long custom fields on the Address Forms of interest.

Validation messages warn the user against common actions that won’t allow a sync to properly proceed.

If audience of previous validation client scripts has been adjusted, consider making the same adjustments for the new validation scripts.

Support for downloading FieldAware Job Task attachments that exceed the maximum file processing limit (10Mb) of NetSuite.

Records referenced by other records (i.e. the customer or contact on the Sales Order or FieldAware Asset) now only need to have previously synced to FieldAware to be selected and no longer also require their "Sync to FieldAware" checkbox to be set.

Fixed a situation where NS users editing a record syncing to a job would unwittingly unassign the job lead if they didn’t have permissions to access the employee record.

Allows the connector to update Sales Order in one step via the FieldAware Sync Restlet instead of the two steps previously needed (one via Webservices and one via the Restlet).

A minor fix in the FieldAware Job Custom Record form makes the Scheduled Date/time field mandatory.

Adds support for syncing serialized and lot numbered assembly items to FA items

When updating the bundle, set “Update deployments” option for the “FieldAware Sync” script

Bugfix for CSV imports

Adds support for using NS item groups to pre-populate jobs with tasks/items created from a Project Task

When updating the bundle, set “Update deployments” option for the two available Client scripts:

Enables global search for all FA uuid custom fields and for SO Job ID, Employee FA user email, and FA Asset serial number.

SuiteApp customizations on the item level won’t show for purchasable items (that can't be used in the SO).

A column field for syncing FieldAware task notes is added on the Sales Order item list. It is necessary to allow this column to exist on SO forms used for syncing to FA.

Two custom fields are added on the Project Task to allow controlling individual project task syncing. The Project level custom fields are re-purposed to control the default states shown on project tasks.

Kit/Package items can now sync to FieldAware items.

Fixes around syncing the correct Company Name when the Customer is an Individual instead of an actual company.

When updating the bundle, set “Update deployments” option for the following scripts:

Decide if you wish to show Field Task Notes on existing SO forms by default:

Open image-20200414-174307.png

If you leave the default of “hide” then after the update you will need to manually show the field on SO forms used to sync to FA (and the default for creation).

Update the label on the form for a Project entity custom field:

If you didn’t select to “show” the Field Task Notes column earlier, now manually show the field on SO forms that are used to sync to FA (and the default for creation via SOAP). Due to NS restrictions, this field must be present on the form for the SO sync to work.

Engineering and bugfix update

Enables updates in Sales Orders and/or FieldAware Jobs to reconcile their contents with the other system when syncing, no longer overwriting changes on the updated system.

The example custom Address Form will be reset. This form is meant as an example and shouldn’t be used directly, so if you’re using it, maybe now is a good time to copy it and customize/use your copy. It is possible that custom fields/associated countries on the existing form will be lost.

If using the example FieldAware address form, copy it and use the copy as default to avoid it being changed.

Notify the FieldAware team to get the reconciliation feature enabled on your account.

The Job Crew of the FieldAware Job is now shown in a multiselect field in Sales Orders. This is read-only field (only flows from FA→NS). Only NS Employees that have synced to FieldAware users will appear on the list as part of the crew.

The Job Worked Hours Custom Record now syncs lat/long start/end locations (if that information is available in FieldAware).

CSV imports of service items should now work.

Apply the new Job Crew custom field on the Sales Order forms you’re using when syncing records to FieldAware (and the default form that will be used when a new record is created from the integration).

​