Field Service for NetSuite Configuration Guide
- About configuring Field Service
After installing the Field Service app, you must define settings in Advanced Inventory Platform Manager, Advanced Inventory Mobile Client, and NetSuite before technicians can run the app. Configuration actions include setting up configuration element values, NetSuite records, and database table replication. You must configure these elements and options for your specific installation environment.
- Configure Field Service for NetSuite
Before users can run the Field Service app in Mobile Client, you must configure settings in Advanced Inventory Platform Manager and NetSuite. We recommend configuring and testing the app in the development environment prior to promoting the app to a production environment. These configuration steps are required in any environment running Field Service.
- About configuring the Field Service for NetSuite configuration elements
The required configuration elements for Field Service for NetSuite are added to Mobile Enterprise Platform when the app is installed. These configuration elements must be configured to support the requirements of your environment.
- About configuring NetSuite for Field Service
The Advanced Inventory Field Service app integrates with your NetSuite Field Service functionality. Each "service order" in the Field Service app corresponds with a project record or case record configured in NetSuite. The app also relies on the tasks created for each project or case. Before using Advanced Inventory Field Service, confirm that the applicable records are accurately configured in NetSuite.
- About configuring data replication for Field Service
The Field Service app supports Advanced Inventory data replication functionality. Data replication is used to transmit data between NetSuite, middle-tier databases, and individual Field Service enabled devices. The data replication feature allows any existing offline Field Service transactions to replicate from the local database to the middle-tier database and, ultimately, to NetSuite.
Loading...
There was a problem loading this topic