Special Upgrade / Install Instructions
If upgrading from a SedonaOffice version prior to 6.0, the following related updates are also required:
FSU Updates - iOS devices must be on iOS version 11 or newer. Please also check the app store for any updates to your FSU app
SedonaWeb - If your company uses SedonaWeb, IT will update your SedonaWeb version at the same time as your SedonaOffice version. This is to ensure the highest level of PCI compliance throughout all applications
SedonaCloud/SedonaAPI 2.0 Setup - If your company uses the SedonaAPI, IT will update your SedonaAPI version at the same time as your SedonaOffice version. This is to ensure compatibility with the SalesAutomation module.
If you are not a SedonaCloud customer, please review the requirements for the new API before requesting the update. For a copy of pre-install requirements please contact: sedonaoffice.support@boldgroup.com
Performing Update - Once you have reviewed all of 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
Version Support
**SedonaCloud Users** - If your company utilizes SedonaCloud in any manner (utilize Sales Automation, Time & Attendance, eForms, SedonaWeb 2.0, or the SedonaCloud API for integrations such as the Manitou integration), you will need to update your SedonaCloud to version 1.24.6 or higher when you update SedonaOffice to 6.1.0.58.
Minimum System Requirements:
• Server is on Microsoft .Net 4.6.1
Features
Bugs
Sedona Email Remittance address missing (13395)
Product: SedonaOffice
Issue: Sedona email remittance does not include the customer’s bill to address like the printed remittance.
Solution: Updated Mandrill template to format the remittance coupon correctly and added the customer’s name and bill-to address.
EFT returned Z Transaction (16086)
Product: SedonaOffice
Issue: When an EFT Transaction is contested, and the transaction is reversed, Forte cannot send the money back to the end customer, so they deposit it back to SedonaOffice customer as a credit.
Solution:
When Forte rejects a refund, it will now be set to Previously Funded.
Collection queue app no longer working (16088)
Product: SedonaOffice
Issue: Collection queue app stopped working on the AWS environment.
Solution: Updated the SedonaOfficeConnectionManager.dll to create the connection string to the database.
POS Crashes (16249)
Product: SedonaOffice
Issue: Point of Sale Module in SedonaOffice 6.1 returns error: “Object reference not set to an instance of an object” if “credit card” is selected as payment method.
Solution: Resolved error and allow using credit card payment method during Point of Sale transaction.
Cannot access Manitou Info Button (15124)
Product: SedonaOffice
Issue: When a customer is pushed from Manitou to SedonaOffice the Manitou Info button does not open the Manitou system screen.
Solution: Fixed stored procedure CS_TP_GetSystemInfo to return system information, even if the customer does not have a bill-to email record in the AR_Customer_Bill_email table.
SO/Manitou integration site address error (16407)
Product: SedonaOffice
Issue: Receiving error trying to save an address in SedonaOffice that is linked to Manitou.
Solution: Resolved error handling. Saving a site address in SedonaOffice for a customer linked to Manitou properly updates Manitou.
New Company Wizard not deleting/truncating the AR_Cycle_Deferred_Income table (16548)
Product: SedonaOffice
Issue: New Company wizard is leaving data in the AR_Cycle_Deferred_Income table.
Solution: Modified New Company Wizard to delete the date from AR_Cycle_Deferred_Income table.
Zero Part Pricing is not working properly (16769)
Product: SedonaOffice
Issue: Issuing a part to a job using Inventory Issues/Returns adds the part price to the job materials list if flagged for zero part pricing.
Solution: Added a check in Inventory Issues/Returns to use a zero rate if the job type is flagged for zero part pricing.
Add YTD Income Statement Report (16077)
Product: SedonaOffice
Issue: YTD Income Statement does not open in SedonaOffice.
Solution: YTD Income Statement was changed and now opens from Report Manager.
Recurring Analysis report errors (16285)
Product: SedonaOffice
Issue: Running the Recurring Analysis report returns error “Run-time error 91: Object variable or with block variable not set”.
Solution: Recurring Analysis report was updated and runs without displaying the “Run-time error 91: Object variable or with block variable not set” error.
ACH Batch Report includes both funded and unfunded (16955)
Product: SedonaOffice
Issue: ACH Batch Report shows funded and unfunded transactions when unfunded is checked.
Solution: Changed ACH Batch report query to correctly identify funded versus unfunded transactions.
User can delete a half-posted cycle (17016)
Product: SedonaOffice
Issue: User posted cycle of invoices where NULL exists in data causes partial posting.
Solution: Handled NULL in stored procedure Cycle_Invoice_add for AR_Customer_Bill. Condition implemented to avoid deleting cycles that are partially posted.
Job parts issue results in incorrect error message (17017)
Product: SedonaOffice
Issue: Receiving error message that parts are out stock for a part that is in stock after removing the out of stock part from the job that generated the original out of stock error message.
Solution: Check on-hand quantity before creating a new job parts issue instead of relying on the status when the grid was first loaded.
POS Sales Tax calculated incorrectly (17019)
Product: SedonaOffice
Issue: Sales tax rounding issues in POS and Refund transactions
Solution: Modified sales tax calculation to round the tax for each tax group before adding it to the accumulated total tax.
ACH/EFT customer search causes error (17215)
Product: SedonaOffice
Issue: During payment processing, customer search returns error “frm:91 object variable or with block variable not set.”
Solution: Don't allow a second customer search to be initiated, while another search is already in progress.
Trouble closing jobs (17216)
Product: SedonaOffice
Issue: Install company is set to complete appointments only (not entering dispatch times on job appointments), when closing the job, a message is displayed to the user: “This job has pending appointments. Do you wish to close the job anyway?”
Solution: Implemented appointment completed check to check pending appointments count
POS customer receipt missing the details of the POS entry (17234)
Product: SedonaOffice
Issue: With Print Receipt option checked on POS Entry the print preview does not display any data.
Solution: Changed the join with the AR_ACH table to pass the ACHId parameter.
POS customer receipt returns run-time error 3021 (17239)
Product: SedonaOffice
Issue: Run-time error 3021 received when printing customer receipt using Microsoft XPS Document Writer
Solution: Changed the join with the AR_ACH table to pass the ACHId parameter.
POS Entry List is blank (17472)
Product: SedonaOffice
Issue: Viewing detail of POS Opening does not list the entries submitted.
Solution: Changed the join in AR_ACH table.
POS Location description changes when record is saved (17446)
Product: SedonaOffice
Issue: Upon saving a new POS location, the description of a POS location is changed.
Solution: Changed the POS Location stored procedure to give each description column a unique name.
