SedonaAPI and SedonaWeb 2.0 - 1.43.1 - 4/5/2023

Enhancements/Features

33447 | Create public delete customer endpoint

We have added DELETE /api/customer/{id} that will delete the specified CustomerId if it has one bill-to, one site, and no other associated information (with a few exceptions as noted below).

A customer cannot be deleted if:

  • It has more than one bill-to
  • It has more than one site
  • Its site has any systems
  • It has any recurring
  • It has been tokenized by a payment processor
  • It has any bank accounts
  • It has any credit cards
  • It has any invoices
  • It has any service tickets
  • It is a master account
  • It has any entries in the GL register
  • It has an advance deposit
  • It is in the cancel queue
  • It has any credit memos
  • It has late fees
  • It has any items (Items tab on Customer form)
  • Its site has any items (Items tab on Site form)
  • It has any Cycle records
  • It has any deposit checks
  • It has any incident records
  • It has any statements
  • It has any jobs
  • It has any point of sale records

If the customer has any of the following, it will be deleted with the customer:

  • Contacts (bill-to, site, or both)
  • Customer notes
  • Critical message
  • WS_Account info (should not exist, in most cases)
  • Aging entries (created automatically when adding a new customer)
  • User-defined information (created automatically when adding a new customer)

This endpoint calls the new SedonaOffice stored procedure Customer_DEL_from_API. The stored proc can be manually created on any 6.2 database - the customer does not have to update SedonaOffice just for this.

If the stored procedure is not found, the response to the API call is "SedonaOffice version is not compatible with this endpoint." This allows SedonaWeb 2.0 to be upgraded separately from SedonaOffice.

Application Corrections

Development ID CRM ID Resolved Issue
n/a n/a
n/a

SedonaAPI

Development ID CRM ID Resolved Issue
26329 00042082, 35082
Cannot enter times on Sedona-X Mobile

Resolved an issue with upcoming appointments not loading by creating and using a new endpoint that does not populate UTC times if they are not needed.

SedonaOffice

Development ID CRM ID Resolved Issue
n/a n/a
n/a

SedonaWeb

Development ID CRM ID Resolved Issue
33434
POST /api/Customer2 subaccount customer number assigned incorrectly

When auto-create customer number is enabled, a new customer that has a master customer will be created with this account number: MasterCode-CustomerNumber. For example, if creating a new child account for master customer number M77, the new child account will be M77-NextCustomerNumber.

Special Upgrade / Install Instructions

If your company uses SedonaWeb 2.0/SedonaAPI 2.0, IT will update the version at the same time as your SedonaOffice upgrade. This is to ensure compatibility with the modules using SedonaWeb 2.0/SedonaAPI 2.0.

Supported Environments

  • This version of SedonaCloud requires SedonaOffice version 6.2.0.11 or above if using SedonaOffice and Sales Automation.
  • Minimum System Requirements: Server is on Microsoft .Net 4.6.1
Was this article helpful?
Thank you for your feedback!
User Icon

Thank you! Your comment has been submitted for approval.