SedonaOffice - 6.2.0.11 - 4/6/2023

01/05/2024 5:24 pm EST

Enhancements/Features

30931 | Won Chargeback EFT History

When a payment is generated in SedonaOffice as a result of a won chargeback, users can see a reference on that payment in the memo field stating that it was a won chargeback transaction. This helps users clearly track the payment history surrounding the transaction.

34445 | Sebis Registration Code

We are now providing our invoice mail service provider, Sebis, with the registration code associated with the records that we are sending so that Sebis can add the code to the invoices they send.

To see this, follow these steps:

On the Accounts Receivable menu, click Print Invoices.
Click Create List. (Note: This opens the Bridgestone Export Wizard, however, the invoice mail service provider is Sebis.

We have added the registration code to the end of type 1 records:

34488 | Add Local Zone column to the equipment grid

On the equipment summary screen, we have added the Local Zone Field.

34489 | Add User Description field on Recurring Summary Screen

On the customer recurring summary screen, we have added the User Description field. This is the description displayed on the Customer Recurring Setup screen and is located in the AR_Customer_Recurring.UserDescription field.

Application Corrections

Accounts Payable

Development ID	CRM ID	Resolved Issue
34536	00071225	Direct Expense Error on Job PO - Error Saving Receipt - Max # of objects in Collection Exceeded Resolved an error generated in loading parts to a warehouse when creating a purchase order by increasing the number of warehouses used from 2000 to 2500.

Development ID

CRM ID

Resolved Issue

34536

00071225

Direct Expense Error on Job PO - Error Saving Receipt - Max # of objects in Collection Exceeded

Resolved an error generated in loading parts to a warehouse when creating a purchase order by increasing the number of warehouses used from 2000 to 2500.

Accounts Receivable

Development ID	CRM ID	Resolved Issue
31092	00057124	Changes to PCI Compliance Update Made changes to the PCI Compliance Update to resolve an issue with different accounts where the customer names were the same, but the sync process appeared to have updated both accounts with the same credit card information.
33137	00068260	Duplicate ACH Processing Payments found Cleaned up code and added logging to isolate and correct the issue. Cleaned up SQL transaction processing. Several instances where a catch would do a rollback even when not in an active transaction. Cleaned up ACH transaction locking. Several instances where a catch would unlock the transaction even though it was not locked or could have been locked by somebody else. Added batch locking. Not having batch locking is likely the cause of the deadlocks. Changed the SEFT locking mechanism (used for transactions and now batches) to try up to 15 times at 1 second intervals. Prior to this change, it would try only 1 time - if the transaction was locked, it would immediately throw an exception, which would cause the transaction to incorrectly get unlocked (because it was locked by somebody else). Now it will retry acquiring the lock, which presumably it should be able to do because the process that had the lock will at some point have finished what it was doing and unlocked the entity, allowing the current process to continue. Improved many error messages with more information. Added more logging to the SEFT_Service_Log table throughout the payment processing dlls and SedonaEFTService. Improved efficiency such as cases where the same information was retrieved from the database more than once. Code cleanup such as readability and removing unused methods/variables. Added needed, missing index for Trans_Reference on AR_ACH. Payment processing retrieves the ACH record by trace number (which is in Trans_Reference column), and the missing index caused SQL to have to do a table scan every time, which is extremely undesirable (time and resource consuming) when looking for a single record. While looking at AR_ACH indexes, noticed that ACH_Id had a non-clustered index with fillfactor of 80. This should be a clustered index with no fillfactor. Added needed, missing index for ACH_Direct_Token on AR_Customer_CC. While looking at AR_Customer_CC indexes, noticed that Customer_CC_Id had a non-clustered index with fillfactor of 80. This should be a clustered index with no fillfactor.
35061	00076673, 76562, 76451,76447, 76636, 76475. 76742, 75856, 76522	Cycle EFT Processing Transactions Rejected - A Task was Canceled This issue has been resolved so that transactions process without error.

Development ID

CRM ID

Resolved Issue

31092

00057124

Changes to PCI Compliance Update

Made changes to the PCI Compliance Update to resolve an issue with different accounts where the customer names were the same, but the sync process appeared to have updated both accounts with the same credit card information.

33137

00068260

Duplicate ACH Processing Payments found

Cleaned up code and added logging to isolate and correct the issue.

Cleaned up SQL transaction processing. Several instances where a catch would do a rollback even when not in an active transaction.
Cleaned up ACH transaction locking. Several instances where a catch would unlock the transaction even though it was not locked or could have been locked by somebody else.
Added batch locking. Not having batch locking is likely the cause of the deadlocks.
Changed the SEFT locking mechanism (used for transactions and now batches) to try up to 15 times at 1 second intervals. Prior to this change, it would try only 1 time - if the transaction was locked, it would immediately throw an exception, which would cause the transaction to incorrectly get unlocked (because it was locked by somebody else). Now it will retry acquiring the lock, which presumably it should be able to do because the process that had the lock will at some point have finished what it was doing and unlocked the entity, allowing the current process to continue.
Improved many error messages with more information.
Added more logging to the SEFT_Service_Log table throughout the payment processing dlls and SedonaEFTService.
Improved efficiency such as cases where the same information was retrieved from the database more than once.
Code cleanup such as readability and removing unused methods/variables.
Added needed, missing index for Trans_Reference on AR_ACH. Payment processing retrieves the ACH record by trace number (which is in Trans_Reference column), and the missing index caused SQL to have to do a table scan every time, which is extremely undesirable (time and resource consuming) when looking for a single record.
While looking at AR_ACH indexes, noticed that ACH_Id had a non-clustered index with fillfactor of 80. This should be a clustered index with no fillfactor.
Added needed, missing index for ACH_Direct_Token on AR_Customer_CC.
While looking at AR_Customer_CC indexes, noticed that Customer_CC_Id had a non-clustered index with fillfactor of 80. This should be a clustered index with no fillfactor.

35061

00076673, 76562, 76451,76447, 76636, 76475. 76742, 75856, 76522

Cycle EFT Processing Transactions Rejected - A Task was Canceled

This issue has been resolved so that transactions process without error.

Client Management

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

Development ID

CRM ID

Resolved Issue

n/a

None

Job Management

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

Development ID

CRM ID

Resolved Issue

n/a

None

General Ledger

Development ID	CRM ID	Resolved Issue
34729	00074791	Double postings to GL for job receipts Resolved this issue by reversing an earlier fix that allowed users to enter both a service ticket and job on the same bill.

Development ID

CRM ID

Resolved Issue

34729

00074791

Double postings to GL for job receipts

Resolved this issue by reversing an earlier fix that allowed users to enter both a service ticket and job on the same bill.

Inventory

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

Development ID

CRM ID

Resolved Issue

n/a

None

Query Builder

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

Development ID

CRM ID

Resolved Issue

n/a

None

Report Manager

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

Development ID

CRM ID

Resolved Issue

n/a

None

Service

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

Development ID

CRM ID

Resolved Issue

n/a

None

Setup

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

Development ID

CRM ID

Resolved Issue

n/a

None

eForms

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

Development ID

CRM ID

Resolved Issue

n/a

None

Sales Automation

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

Development ID

CRM ID

Resolved Issue

n/a

None

Time & Attendance

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

Development ID

CRM ID

Resolved Issue

n/a

None

Integrations

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

Development ID

CRM ID

Resolved Issue

n/a

None

Stored Procedures

Updated Stored Procedures:

None

New stored procedures:

Customer_DEL_from_API (called by SedonaAPI 2.0)

Database Changes

Special Upgrade / Installation Instructions

If upgrading from a SedonaOffice version prior to 6.0, the following related updates are also required:

Legacy SedonaWeb 1.0 - Be aware that if your company uses Legacy SedonaWeb 1.0 (latest version 2.7.80) with SedonaOffice version 6.2.0.8 and earlier, we recommend that you transition to using SedonaWeb 2.0.

Legacy SedonaWeb 1.0 is not for SedonaOffice 6.2.0.9 or later.

SedonaWeb 2.0/SedonaAPI 2.0 Setup - If your company uses the SedonaWeb/SedonaAPI 2.0, IT will update your SedonaAPI version at the same time as your SedonaOffice version. This is to ensure compatibility with the Sales Automation module.

If your company uses SedonaAPI in any manner (Sales Automation, Time & Attendance, eForms, or the SedonaAPI for integrations such as the Manitou integration), you need to update SedonaWeb/SedonaAPI to version 1.43.1 (or higher) when you update SedonaOffice to 6.2.0.11.

Performing Update - Once you have reviewed all the above information, and followed all preparation steps, contact SedonaOffice support. We will note on your account that you have received the Release Notes and are ready for update. SedonaOffice IT will then contact you to schedule your update.

Supported Environments

Minimum System Requirements:

Server is on Microsoft .Net 4.6.1

Was this article helpful?