ASP.NET Web API Help Page

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

gets all the related mainlines

gets all the related mainlines

gets all the related mainlines

gets all the related mainlines

gets all the related mainlines

gets all the related mainlines

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

returns the number of messages in the Message table. Used for polling to make sure the webpage doesn't need to reload the entire message list again.

returns the number of messages in the Message table. Used for polling to make sure the webpage doesn't need to reload the entire message list again.

returns the number of messages in the Message table. Used for polling to make sure the webpage doesn't need to reload the entire message list again.

returns the number of messages in the Message table. Used for polling to make sure the webpage doesn't need to reload the entire message list again.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

This executes a request for the break-out lines for any invividual line item

By Posting a list of LineBreakout Objects, including the parent line item ID, we can break that item into multiple lines

Flags the Breakout Item (JobLineItem) as "deleted" by setting the DeleteBreakout column in the table.

This executes a request for the break-out lines for any invividual line item

By Posting a list of LineBreakout Objects, including the parent line item ID, we can break that item into multiple lines

Flags the Breakout Item (JobLineItem) as "deleted" by setting the DeleteBreakout column in the table.

This executes a request for the break-out lines for any invividual line item

By Posting a list of LineBreakout Objects, including the parent line item ID, we can break that item into multiple lines

Flags the Breakout Item (JobLineItem) as "deleted" by setting the DeleteBreakout column in the table.

This executes a request for the break-out lines for any invividual line item

By Posting a list of LineBreakout Objects, including the parent line item ID, we can break that item into multiple lines

Flags the Breakout Item (JobLineItem) as "deleted" by setting the DeleteBreakout column in the table.

Returns a list of tasks assigned to the user based upon the sessionid

Returns an individal task based upon the ID

Posting the entire Task object will insert it into the system. The TaskID is ignored, so if you're updating a record and use the POST instead of a PUT, you'll actually be creating a new one. if the update was successful you'll get back the full UserTask object, including a TaskID. If not, the taskID will be -1

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

this sets the task status to -1. a successful delete returns a 1 and a failure a -1

Returns a list of tasks assigned to the user based upon the sessionid

Returns an individal task based upon the ID

Posting the entire Task object will insert it into the system. The TaskID is ignored, so if you're updating a record and use the POST instead of a PUT, you'll actually be creating a new one. if the update was successful you'll get back the full UserTask object, including a TaskID. If not, the taskID will be -1

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

this sets the task status to -1. a successful delete returns a 1 and a failure a -1

Posting the entire Task object will insert it into the system. The TaskID is ignored, so if you're updating a record and use the POST instead of a PUT, you'll actually be creating a new one. if the update was successful you'll get back the full UserTask object, including a TaskID. If not, the taskID will be -1

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

this sets the task status to -1. a successful delete returns a 1 and a failure a -1

Returns a list of tasks assigned to the user based upon the sessionid

Returns an individal task based upon the ID

Posting the entire Task object will insert it into the system. The TaskID is ignored, so if you're updating a record and use the POST instead of a PUT, you'll actually be creating a new one. if the update was successful you'll get back the full UserTask object, including a TaskID. If not, the taskID will be -1

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

this sets the task status to -1. a successful delete returns a 1 and a failure a -1

Retrieves a list of all jobs

Retreives a specific job

This will create a new job record

Used to update jobs with existing Job IDs

Used to alter status column to "Deleted" in Upload table.

Retrieves a list of all jobs

Retreives a specific job

This will create a new job record

Used to update jobs with existing Job IDs

Used to alter status column to "Deleted" in Upload table.

This will create a new job record

Used to update jobs with existing Job IDs

Used to alter status column to "Deleted" in Upload table.

Retrieves a list of all jobs

Retreives a specific job

This will create a new job record

Used to update jobs with existing Job IDs

Used to alter status column to "Deleted" in Upload table.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

This pulls a list of purchase orders related to the job

Links Jobs to Purchase Orders and Quotes.

This pulls a list of purchase orders related to the job

Links Jobs to Purchase Orders and Quotes.

This pulls a list of purchase orders related to the job

Links Jobs to Purchase Orders and Quotes.

This pulls a list of purchase orders related to the job

Links Jobs to Purchase Orders and Quotes.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

Retrieves rows from the Customer table. If id is set to zero, all rows are retrieved. Otherwise only the row with the associated id is returned.

Controller to insert a new row into the Customer table.

Controller to update a row in the Customer table.

Retrieves rows from the Customer table. If id is set to zero, all rows are retrieved. Otherwise only the row with the associated id is returned.

Controller to insert a new row into the Customer table.

Controller to update a row in the Customer table.

Retrieves rows from the Customer table. If id is set to zero, all rows are retrieved. Otherwise only the row with the associated id is returned.

Controller to insert a new row into the Customer table.

Controller to update a row in the Customer table.

Retrieves rows from the Customer table. If id is set to zero, all rows are retrieved. Otherwise only the row with the associated id is returned.

Controller to insert a new row into the Customer table.

Controller to update a row in the Customer table.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

This will return a full list of all SiteReviewResponses

Controller to insert a new row into the SiteReviewResponse table.

Controller to update a row in the SiteReviewResponse table.

This will return a full list of all SiteReviewResponses

Controller to insert a new row into the SiteReviewResponse table.

Controller to update a row in the SiteReviewResponse table.

This will return a full list of all SiteReviewResponses

Controller to insert a new row into the SiteReviewResponse table.

Controller to update a row in the SiteReviewResponse table.

This will return a full list of all SiteReviewResponses

Controller to insert a new row into the SiteReviewResponse table.

Controller to update a row in the SiteReviewResponse table.

No documentation available.

We're sending the parent, which is the job folder, the name of the folder, which is "locations", the list of subfolders, which is one for each location on the job. Then, we share the locations folder and the job package folder with the crew.

No documentation available.

We're sending the parent, which is the job folder, the name of the folder, which is "locations", the list of subfolders, which is one for each location on the job. Then, we share the locations folder and the job package folder with the crew.

No documentation available.

We're sending the parent, which is the job folder, the name of the folder, which is "locations", the list of subfolders, which is one for each location on the job. Then, we share the locations folder and the job package folder with the crew.

No documentation available.

We're sending the parent, which is the job folder, the name of the folder, which is "locations", the list of subfolders, which is one for each location on the job. Then, we share the locations folder and the job package folder with the crew.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

This will get the indiviaual accrual item if necessary

No documentation available.

This will get the indiviaual accrual item if necessary

No documentation available.

This will get the indiviaual accrual item if necessary

No documentation available.

This will get the indiviaual accrual item if necessary

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

Returns all rows as JSON

Returns specific PurchaseOrderItem as JSON

Inserts a new Purchase Order Item, and returns the newly inserted row.

Updates a Purchase Order Item.

Sets the deleted flag in the database for the row. Rows are not truly deleted.

Returns all rows as JSON

Returns specific PurchaseOrderItem as JSON

Inserts a new Purchase Order Item, and returns the newly inserted row.

Updates a Purchase Order Item.

Sets the deleted flag in the database for the row. Rows are not truly deleted.

Inserts a new Purchase Order Item, and returns the newly inserted row.

Updates a Purchase Order Item.

Sets the deleted flag in the database for the row. Rows are not truly deleted.

Returns all rows as JSON

Returns specific PurchaseOrderItem as JSON

Inserts a new Purchase Order Item, and returns the newly inserted row.

Updates a Purchase Order Item.

Sets the deleted flag in the database for the row. Rows are not truly deleted.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

Returns one row Material invoiced if an MaterialInvoiceID other than zero is passed. If MaterialInvoiceID = 0, all rows in the table are returned.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

Returns one row Material invoiced if an MaterialInvoiceID other than zero is passed. If MaterialInvoiceID = 0, all rows in the table are returned.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

Returns one row Material invoiced if an MaterialInvoiceID other than zero is passed. If MaterialInvoiceID = 0, all rows in the table are returned.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

Returns one row Material invoiced if an MaterialInvoiceID other than zero is passed. If MaterialInvoiceID = 0, all rows in the table are returned.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

This will return a full list of all TrackerITems

This will return a full list of all Job Line Items for a Job.

This updates Job Line Item.

This will return a full list of all TrackerITems

This will return a full list of all Job Line Items for a Job.

This updates Job Line Item.

This updates Job Line Item.

This will return a full list of all TrackerITems

This will return a full list of all Job Line Items for a Job.

This updates Job Line Item.

No documentation available.

A list of all tests for a selected node

No documentation available.

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

A list of all tests for a selected node

No documentation available.

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

A list of all tests for a selected node

No documentation available.

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

This is the standard "return a list" of whatever the sql statement requests as JSON

Here we will use the exact same code as the first GET statement, but limit it to a single row.It is best if we define an object, instantiate it and then return it in the OK statement.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

This is the standard "return a list" of whatever the sql statement requests as JSON

Here we will use the exact same code as the first GET statement, but limit it to a single row.It is best if we define an object, instantiate it and then return it in the OK statement.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

This is the standard "return a list" of whatever the sql statement requests as JSON

Here we will use the exact same code as the first GET statement, but limit it to a single row.It is best if we define an object, instantiate it and then return it in the OK statement.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

This returns a set directly from vwTracker in the database (showing only active jobs)

By adding the JobID in the tracker path, we can restrict it to a specific job.

This returns a set directly from vwTracker in the database (showing only active jobs)

By adding the JobID in the tracker path, we can restrict it to a specific job.

This returns a set directly from vwTracker in the database (showing only active jobs)

By adding the JobID in the tracker path, we can restrict it to a specific job.

This is the standard "return a list" of whatever the sql statement requests as JSON

Here we will use the exact same code as the first GET statement, but limit it to a single row.It is best if we define an object, instantiate it and then return it in the OK statement.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

This is the standard "return a list" of whatever the sql statement requests as JSON

Here we will use the exact same code as the first GET statement, but limit it to a single row.It is best if we define an object, instantiate it and then return it in the OK statement.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

This is the standard "return a list" of whatever the sql statement requests as JSON

Here we will use the exact same code as the first GET statement, but limit it to a single row.It is best if we define an object, instantiate it and then return it in the OK statement.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

Splits PDF files

Splits PDF files

Splits PDF files

Splits PDF files

Returns single row from InternalContact if an InternalContactID other than zero is passed. If InternalContactID = 0, all rows in the table are returned.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

Returns single row from InternalContact if an InternalContactID other than zero is passed. If InternalContactID = 0, all rows in the table are returned.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

Returns single row from InternalContact if an InternalContactID other than zero is passed. If InternalContactID = 0, all rows in the table are returned.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

Returns single row from InternalContact if an InternalContactID other than zero is passed. If InternalContactID = 0, all rows in the table are returned.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

No documentation available.

No documentation available.

No documentation available.

No documentation available.

This gets all unlinked purchase orders

This will return all the PurchaseOrders associated with a job

This will associate a PO with a Job.

sending the purchase orderid will remove it and all its products from the job.

This gets all unlinked purchase orders

This will return all the PurchaseOrders associated with a job

This will associate a PO with a Job.

sending the purchase orderid will remove it and all its products from the job.

This gets all unlinked purchase orders

This will return all the PurchaseOrders associated with a job

This will associate a PO with a Job.

sending the purchase orderid will remove it and all its products from the job.

This gets all unlinked purchase orders

This will return all the PurchaseOrders associated with a job

This will associate a PO with a Job.

sending the purchase orderid will remove it and all its products from the job.

This returns a list of all Quotes. In this case "id" is hardcoded as zero, and not passed as a parameter to the method. The stored procedure in the database uses this value to retrieve all rows.

This returns a specific row in the PurchaseOrderTable. This method can be used to retrieve Quotes as well.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

This returns a list of all Quotes. In this case "id" is hardcoded as zero, and not passed as a parameter to the method. The stored procedure in the database uses this value to retrieve all rows.

This returns a specific row in the PurchaseOrderTable. This method can be used to retrieve Quotes as well.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

This returns a list of all Quotes. In this case "id" is hardcoded as zero, and not passed as a parameter to the method. The stored procedure in the database uses this value to retrieve all rows.

This returns a specific row in the PurchaseOrderTable. This method can be used to retrieve Quotes as well.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

This will return a full list of all TrackerITems

This will return a full list of all TrackerITems

This will add a new Tracker Item to the ITTracker table and return the full object plus the new ID

This updates an IT Tracker Item. Make sure to include the IT TrackerID in the object

This will return a full list of all TrackerITems

This will return a full list of all TrackerITems

This will add a new Tracker Item to the ITTracker table and return the full object plus the new ID

This updates an IT Tracker Item. Make sure to include the IT TrackerID in the object

This will return a full list of all TrackerITems

This will return a full list of all TrackerITems

This will add a new Tracker Item to the ITTracker table and return the full object plus the new ID

This updates an IT Tracker Item. Make sure to include the IT TrackerID in the object

This will return a full list of all TrackerITems

This will return a full list of all TrackerITems

This will add a new Tracker Item to the ITTracker table and return the full object plus the new ID

This updates an IT Tracker Item. Make sure to include the IT TrackerID in the object

No documentation available.

No documentation available.

No documentation available.

No documentation available.

This returns all the material items on a job with the billed and backout calculated by the week selected. Calculations have not yet been implemented.

This returns all the material items on a job with the billed and backout calculated by the week selected. Calculations have not yet been implemented.

This returns all the material items on a job with the billed and backout calculated by the week selected. Calculations have not yet been implemented.

This returns all the material items on a job with the billed and backout calculated by the week selected. Calculations have not yet been implemented.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

Get status of server

Get status of server

Get status of server

Get status of server

No documentation available.

No documentation available.

No documentation available.

No documentation available.

Retrieves a list of users

Retreives a specific User

Used to update users with existing user IDs

Used to update users with existing user IDs

Retrieves a list of users

Retreives a specific User

Used to update users with existing user IDs

Used to update users with existing user IDs

Used to update users with existing user IDs

Used to update users with existing user IDs

Retrieves a list of users

Retreives a specific User

Used to update users with existing user IDs

Used to update users with existing user IDs

Retrieves all active job costs for a specific job. Inactive job costs have their flags set to "Deleted".

Retrieves a specific Job Cost entry.

Adds a new Job Cost to a Job, and returns the newly inserted row if the insert was successful.

Updates a Job Cost entry.

Sets the "Deleted" column to 1 to flag the Job Cost as no longer valid for the specified Job. A successful delete returns the row from the database. An error returns the SQL statement that attempted to do the delete.

Retrieves all active job costs for a specific job. Inactive job costs have their flags set to "Deleted".

Retrieves a specific Job Cost entry.

Adds a new Job Cost to a Job, and returns the newly inserted row if the insert was successful.

Updates a Job Cost entry.

Sets the "Deleted" column to 1 to flag the Job Cost as no longer valid for the specified Job. A successful delete returns the row from the database. An error returns the SQL statement that attempted to do the delete.

Retrieves all active job costs for a specific job. Inactive job costs have their flags set to "Deleted".

Retrieves a specific Job Cost entry.

Adds a new Job Cost to a Job, and returns the newly inserted row if the insert was successful.

Updates a Job Cost entry.

Sets the "Deleted" column to 1 to flag the Job Cost as no longer valid for the specified Job. A successful delete returns the row from the database. An error returns the SQL statement that attempted to do the delete.

Retrieves all active job costs for a specific job. Inactive job costs have their flags set to "Deleted".

Retrieves a specific Job Cost entry.

Adds a new Job Cost to a Job, and returns the newly inserted row if the insert was successful.

Updates a Job Cost entry.

Sets the "Deleted" column to 1 to flag the Job Cost as no longer valid for the specified Job. A successful delete returns the row from the database. An error returns the SQL statement that attempted to do the delete.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

gets all the related mainlines

gets all the related mainlines

gets all the related mainlines

gets all the related mainlines

Retrieves rows from the Contact table. If id is set to zero and CustomerID is set to zero, all rows are retrieved. If id is set to zero and CustomerID is non-zero, all Contacts for that Customer are return. Otherwise the row with the associated id is returned.

Controller to insert a new row into the Contact table.

Controller to update a row in the Contact table.

Retrieves rows from the Contact table. If id is set to zero and CustomerID is set to zero, all rows are retrieved. If id is set to zero and CustomerID is non-zero, all Contacts for that Customer are return. Otherwise the row with the associated id is returned.

Controller to insert a new row into the Contact table.

Controller to update a row in the Contact table.

Retrieves rows from the Contact table. If id is set to zero and CustomerID is set to zero, all rows are retrieved. If id is set to zero and CustomerID is non-zero, all Contacts for that Customer are return. Otherwise the row with the associated id is returned.

Controller to insert a new row into the Contact table.

Controller to update a row in the Contact table.

Retrieves rows from the Contact table. If id is set to zero and CustomerID is set to zero, all rows are retrieved. If id is set to zero and CustomerID is non-zero, all Contacts for that Customer are return. Otherwise the row with the associated id is returned.

Controller to insert a new row into the Contact table.

Controller to update a row in the Contact table.

Returns rows from wildcard query of JobInvoiceItem table as JSON

Here we will use the exact same code as the first GET statement, but limit it to a single row.

Returns the inserted JobInvoiceItem object as defined in JSON if the update was successful. If the insert was not successful, an error message is returned.

Handled the same as a "Post". Post and put are defined in the same SQL stored procedure, newJobInvoiceItem.

Returns rows from wildcard query of JobInvoiceItem table as JSON

Here we will use the exact same code as the first GET statement, but limit it to a single row.

Returns the inserted JobInvoiceItem object as defined in JSON if the update was successful. If the insert was not successful, an error message is returned.

Handled the same as a "Post". Post and put are defined in the same SQL stored procedure, newJobInvoiceItem.

Returns rows from wildcard query of JobInvoiceItem table as JSON

Here we will use the exact same code as the first GET statement, but limit it to a single row.

Returns the inserted JobInvoiceItem object as defined in JSON if the update was successful. If the insert was not successful, an error message is returned.

Handled the same as a "Post". Post and put are defined in the same SQL stored procedure, newJobInvoiceItem.

Returns rows from wildcard query of JobInvoiceItem table as JSON

Here we will use the exact same code as the first GET statement, but limit it to a single row.

Returns the inserted JobInvoiceItem object as defined in JSON if the update was successful. If the insert was not successful, an error message is returned.

Handled the same as a "Post". Post and put are defined in the same SQL stored procedure, newJobInvoiceItem.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

Retrieves rows from the NodeLocalMedia table. If id is set to zero, all rows are retrieved. Otherwise only the row with the associated id is returned.

Controller to insert a new row into the NodeLocalMedia table.

Controller to update a row in the NodeLocalMedia table.

No documentation available.

Retrieves rows from the NodeLocalMedia table. If id is set to zero, all rows are retrieved. Otherwise only the row with the associated id is returned.

Controller to insert a new row into the NodeLocalMedia table.

Controller to update a row in the NodeLocalMedia table.

No documentation available.

Retrieves rows from the NodeLocalMedia table. If id is set to zero, all rows are retrieved. Otherwise only the row with the associated id is returned.

Controller to insert a new row into the NodeLocalMedia table.

Controller to update a row in the NodeLocalMedia table.

No documentation available.

Retrieves rows from the NodeLocalMedia table. If id is set to zero, all rows are retrieved. Otherwise only the row with the associated id is returned.

Controller to insert a new row into the NodeLocalMedia table.

Controller to update a row in the NodeLocalMedia table.

No documentation available.

This is the standard "return a list" of whatever the sql statement requests as JSON

Here we will use the exact same code as the first GET statement, but limit it to a single row.It is best if we define an object, instantiate it and then return it in the OK statement.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

This is the standard "return a list" of whatever the sql statement requests as JSON

Here we will use the exact same code as the first GET statement, but limit it to a single row.It is best if we define an object, instantiate it and then return it in the OK statement.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

This is the standard "return a list" of whatever the sql statement requests as JSON

Here we will use the exact same code as the first GET statement, but limit it to a single row.It is best if we define an object, instantiate it and then return it in the OK statement.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

No documentation available.

No documentation available.

No documentation available.

No documentation available.

Retrieves all accruals and invoiced Job Line Items for a particular job. These are summarized by week.

Retrieves all accruals and invoiced Job Line Items for a particular job. These are summarized by week.

Retrieves all accruals and invoiced Job Line Items for a particular job. These are summarized by week.

Retrieves all accruals and invoiced Job Line Items for a particular job. These are summarized by week.

This will return a full list of all TrackerITems

Controller to insert a new row into the InspectionSummaryText table.

Controller to update a row in the InspectionSummaryText table.

This will return a full list of all TrackerITems

Controller to insert a new row into the InspectionSummaryText table.

Controller to update a row in the InspectionSummaryText table.

This will return a full list of all TrackerITems

Controller to insert a new row into the InspectionSummaryText table.

Controller to update a row in the InspectionSummaryText table.

This will return a full list of all TrackerITems

Controller to insert a new row into the InspectionSummaryText table.

Controller to update a row in the InspectionSummaryText table.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

This will retreive the contents of a directory in Amazon S3

No documentation available.

No documentation available.

No documentation available.

This will retreive the contents of a directory in Amazon S3

No documentation available.

No documentation available.

No documentation available.

This will retreive the contents of a directory in Amazon S3

No documentation available.

No documentation available.

No documentation available.

This will retreive the contents of a directory in Amazon S3

No documentation available.

No documentation available.

This is the standard "return a list" of whatever the sql statement requests as JSON

No documentation available.

This is the standard "return a list" of whatever the sql statement requests as JSON

No documentation available.

This is the standard "return a list" of whatever the sql statement requests as JSON

No documentation available.

This is the standard "return a list" of whatever the sql statement requests as JSON

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

This returns the basic material for the job for the current week

Here we will use the exact same code as the first GET statement, but limit it to a single row. It is best if we define an object, instantiate it and then return it in the OK statement. The "Unused" integer is there to differentiate this get from the other.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

This returns the basic material for the job for the current week

Here we will use the exact same code as the first GET statement, but limit it to a single row. It is best if we define an object, instantiate it and then return it in the OK statement. The "Unused" integer is there to differentiate this get from the other.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

This returns the basic material for the job for the current week

Here we will use the exact same code as the first GET statement, but limit it to a single row. It is best if we define an object, instantiate it and then return it in the OK statement. The "Unused" integer is there to differentiate this get from the other.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

This returns the basic material for the job for the current week

Here we will use the exact same code as the first GET statement, but limit it to a single row. It is best if we define an object, instantiate it and then return it in the OK statement. The "Unused" integer is there to differentiate this get from the other.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

This is the standard "return a list" of whatever the sql statement requests as JSON

AuthorID and Comment are all that's required for posting.

AuthorID, ParentMessageID and Comment are all that's required for this method.

This is the standard "return a list" of whatever the sql statement requests as JSON

AuthorID and Comment are all that's required for posting.

AuthorID, ParentMessageID and Comment are all that's required for this method.

This is the standard "return a list" of whatever the sql statement requests as JSON

AuthorID and Comment are all that's required for posting.

AuthorID, ParentMessageID and Comment are all that's required for this method.

This is the standard "return a list" of whatever the sql statement requests as JSON

AuthorID and Comment are all that's required for posting.

AuthorID, ParentMessageID and Comment are all that's required for this method.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

This is the standard "return a list" of whatever the sql statement requests as JSON

Here we will use the exact same code as the first GET statement, but limit it to a single row.It is best if we define an object, instantiate it and then return it in the OK statement.

This gets the total, a sum of the amounts invoiced, and difference between this total and sum for Material or Costs for a Job that have been incurred up to the week entered. Key for determining whether it is Material or Costs that are returned is the value of "type". For Material this should be set equal to the string, "Material". All other values return Costs. Additional parameters are ItemID (BillingWeekID), id (JobID), and sid (SessionID).

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

No documentation available.

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

This is the standard "return a list" of whatever the sql statement requests as JSON

Here we will use the exact same code as the first GET statement, but limit it to a single row.It is best if we define an object, instantiate it and then return it in the OK statement.

This gets the total, a sum of the amounts invoiced, and difference between this total and sum for Material or Costs for a Job that have been incurred up to the week entered. Key for determining whether it is Material or Costs that are returned is the value of "type". For Material this should be set equal to the string, "Material". All other values return Costs. Additional parameters are ItemID (BillingWeekID), id (JobID), and sid (SessionID).

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

No documentation available.

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

This is the standard "return a list" of whatever the sql statement requests as JSON

Here we will use the exact same code as the first GET statement, but limit it to a single row.It is best if we define an object, instantiate it and then return it in the OK statement.

This gets the total, a sum of the amounts invoiced, and difference between this total and sum for Material or Costs for a Job that have been incurred up to the week entered. Key for determining whether it is Material or Costs that are returned is the value of "type". For Material this should be set equal to the string, "Material". All other values return Costs. Additional parameters are ItemID (BillingWeekID), id (JobID), and sid (SessionID).

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

No documentation available.

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

This is the standard "return a list" of whatever the sql statement requests as JSON

Here we will use the exact same code as the first GET statement, but limit it to a single row.It is best if we define an object, instantiate it and then return it in the OK statement.

This gets the total, a sum of the amounts invoiced, and difference between this total and sum for Material or Costs for a Job that have been incurred up to the week entered. Key for determining whether it is Material or Costs that are returned is the value of "type". For Material this should be set equal to the string, "Material". All other values return Costs. Additional parameters are ItemID (BillingWeekID), id (JobID), and sid (SessionID).

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

No documentation available.

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

This is the standard "return a list" of whatever the sql statement requests as JSON

Here we will use the exact same code as the first GET statement, but limit it to a single row.It is best if we define an object, instantiate it and then return it in the OK statement.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

This is the standard "return a list" of whatever the sql statement requests as JSON

Here we will use the exact same code as the first GET statement, but limit it to a single row.It is best if we define an object, instantiate it and then return it in the OK statement.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

This is the standard "return a list" of whatever the sql statement requests as JSON

Here we will use the exact same code as the first GET statement, but limit it to a single row.It is best if we define an object, instantiate it and then return it in the OK statement.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

This is the standard "return a list" of whatever the sql statement requests as JSON

Here we will use the exact same code as the first GET statement, but limit it to a single row.It is best if we define an object, instantiate it and then return it in the OK statement.

Once you know what's coming, you define a custom object (or define a model) to match the JSON, then instead of "JObject", you use that.You do the updates and return the updated object if the update was successful if not, you'll change the response object to empty or send some message back.

we handle this the exact same way as a POST, except it is used for "update" statements rather than inserts

this is never a real delete, but rather sends and update to the DB to set the current record to "deleted" a successful delete returns a 1 and a failure a -1

Retrieves Job Line Items including Breakouts along with Accruals and Invoiced amounts by week.

Retrieves Job Line Items including Breakouts along with Accruals and Invoiced amounts by week.

Retrieves Job Line Items including Breakouts along with Accruals and Invoiced amounts by week.

Retrieves Job Line Items including Breakouts along with Accruals and Invoiced amounts by week.

No documentation available.

No documentation available.

No documentation available.

No documentation available.

Returns all Purchase Orders. as an object array of PurchaseOrder

Gets specific Purchase Order.

This will add a new purchase order to the system. Simply send the Purchase Order Object and a current Session ID. The return will be a purchase order object that includes the new ID as well as any automatically assigned defaults.

This updates the purchase order. Send the PurchaseOrder object along with the SID

Returns all Purchase Orders. as an object array of PurchaseOrder

Gets specific Purchase Order.

This will add a new purchase order to the system. Simply send the Purchase Order Object and a current Session ID. The return will be a purchase order object that includes the new ID as well as any automatically assigned defaults.

This updates the purchase order. Send the PurchaseOrder object along with the SID

This will add a new purchase order to the system. Simply send the Purchase Order Object and a current Session ID. The return will be a purchase order object that includes the new ID as well as any automatically assigned defaults.

This updates the purchase order. Send the PurchaseOrder object along with the SID

Returns all Purchase Orders. as an object array of PurchaseOrder

Gets specific Purchase Order.

This will add a new purchase order to the system. Simply send the Purchase Order Object and a current Session ID. The return will be a purchase order object that includes the new ID as well as any automatically assigned defaults.

This updates the purchase order. Send the PurchaseOrder object along with the SID

No documentation available.

No documentation available.

No documentation available.