Project (Job)
You use the project record to manage company initiatives.
The project record is defined in the listRel (relationships) XSD, where it is called Job.
To use the project record, you must have the Projects feature enabled at Setup > Company > Enable Features, on the Company tab. If you plan to do advanced project tracking, you must also enable Project Management. If you do not see the Project Management box, your company must first purchase the Project Management add-on from NetSuite.
To access the project record in the UI, choose Lists > Relationships > Projects (or Jobs). For help working with projects manually, see Projects.
For more on using SOAP web services to interact with projects, see the following:
Starting with the 2008.2 version of NetSuite, the Job record was renamed to Project, but if you have existing code that references the Job record, this code will not break. The name change applies to external UI labels only. You should continue to reference the Job complex type in your code.
Supported Operations
The following operations can be used with the project record:
add | addList | attach / detach | delete | deleteList | get | getDeleted | getList | getSavedSearch | getSelectValue | search | searchMoreWithId | update | updateList | upsert | upsertList
You can also use the asynchronous equivalents of SOAP web services list operations. For information about asynchronous operations, see SOAP Web Services Asynchronous Operations. For more information about request processing, see Synchronous Versus Asynchronous Request Processing.
Field Definitions
The SOAP Schema Browser includes definitions for all body fields, sublist fields, search filters, and search joins available to this record. For details, see the SOAP Schema Browser’s project reference page. For information about using this tool, see SOAP Schema Browser.
Usage Notes
When using SOAP web services, the behavior of the Resources sublist differs slightly from the behavior in the UI. Specifically, in the UI, each line must have a unique value in the Name field. Further, in the UI, you can select more than one role for each resource.
With SOAP web services, if you want to add a resource that has three different roles, you set up your code as if you are adding three sublist records for that resource — one for each role. The jobResource values are not required to be unique. To see an example, refer to Adding Resources Example Two. Note that after you complete the add operation, the Resources sublist in the UI looks the same as it would if you had manually added one line for the resource, with multiple roles specified on that line, as shown in the illustration above.