AyaNova 7.x Maintenance Update Fixes
The latest AyaNova set up file includes all update fixes - you do not need to apply each fix individually, you can just update to the latest.
As of AyaNova 7.4, a current license subscription is required to be able to update to the latest version.
Purchase your subscription license today via http://www.ayanova.com/purchase_AyaNova_online.htm
New 7.0.3 setup files released Feb 22 2011
Issue Resolved:
Units Text1, Text2, Text3 and Text4 fields now indexed for searching
Previously entered unit records that have any text entered in any of those 4 fields are updated automatically via schema update.
Update to the latest AyaNova 7 to resolve this issue
New 7.0.2.0 setup files released Feb 15 2011
minor change only affecting the following:
Minor Issue Resolved:
If attempt to customize a menu option (i.e. to change the size of the menu icons) now no longer receive error message Object reference not set to an instance of an object
Update to the latest AyaNova 7 to resolve this issue
New setup files released Feb 14 2011
Minor Issue Resolved:
QBI plugin 7.0.2.0 - Removed the change made to QBI to load all clients regardless of what character their QB client’s name starts with that was introduced in 7.0.1.0 fix
That initial feature would intermittently result in an error for some QB users An exception occurred! Type:UTFDataFormatException, Message:invalid byte 1 (?) of a 1-byte sequence.SAXParseException in some databases because of a hidden record that is not normally ever accessed or a corrupted record that is not normally accessed.
So to prevent confusion, have removed the change.
QBI is now back to loading active QuickBooks clients that names start with either a number or regular alphabet letters. If you have an active QuickBooks client whose name starts with a character other than a number of regular alphabet, just edit that client’s name before loading QBI.
Latest AyaNova setup file at http://www.ayanova.com/download.htm also includes this.
Replacement file released January 26 2011 for AyaNova program folder IF had installed 7.0.1.0 before Jan 26th.
Minor Issue Resolved:
Error message CASE 1387 ERROR: AyaBizUtils->Right(StringVersion) - RootObject rights being checked is Workorder! that occurs if searching via Search Database attempts to return a wikipage tied to a workorder.
Update to the latest AyaNova 7 to resolve this issue
New WBI setup file released January 25 2011
Issue Resolved:
WBI Client - if WBI client is member of security group that has Forbidden rights set for Object.WorkorderService, the Service Workorder menu option will not even show on the menu bar (makes it easier for the client as don’t even have to explain it as not needed).
Update to the latest AyaNova and WBI 7 to resolve this issue
7.0.2.0 setup files released January 25 2011 for OLI setup
Minor Issue Resolved:
OLI - resolved issue with generating a service workorder or a schedule marker from an email when connecting through an AyaNova Data Portal connection.
Update to the latest AyaNova and OLI 7 to resolve this issue
7.0.1.0 setup files released January 24 2011
Minor Issue Resolved:
AyaNova - Password masking now occurs with XP and Windows 2003
QBI - resolved issue if QuickBooks clients start with a character other than a letter, will now display in the Map & Import list (i.e. if previously had a client called #1 Plumbing, that client won’t display because of the # as the first character)
OLI - resolved issue with client selection window not displaying when generating a service workorder from an email, or not displaying the AyaNova schedule marker window when generating a schedule marker from an email
Nov 24 2011 - GTZW HotFix 9 (see instructions in first post in this thread on how to apply if require these fixes and improvements)
Resolves issue where under certain circumstances a contract part discount would not be applied to a part that was generated on a workorder from a purchase order receipt on a out of stock request
Nov 9 2011 - AyaNova.exe HotFix 10 and GTZW HotFix 8 (see instructions in first post in this thread on how to apply if require these fixes and improvements)
Resolves issue if have used the Customize… feature on the service workorder disabling the Project label field which results in unable to Save or Save & Exit if make changes but have not clicked elsewhere before clicking on Save or Save & Exit.
October 13 2011 - AyaNova.exe HotFix 9 and GTZW HotFix 7 (see instructions in first post in this thread on how to apply if require these fixes and improvements)
Resolves error message that can occur in Search Database “CASE 1387 ERROR: AyaBizUtils->Right(StringVersion) - RootObject rights being checked is Workorder!” in some circumstances when results include wiki page for workorder.
October 11 2011 - AyaNova.exe HotFix 8 and GTZW HotFix 6
Resolves error message Incorrect syntax near ‘,’ that can occur due to custom filtering on a currency column when regional settings on your computer is set to a region that uses a comma (,) for decimal symbol and period (.) for digit grouping symbol
July 29 2011 - new AyaNovaSetup.exe released that includes selection for installing PTI for use with Peachtree 2012
May 4 2011 AyaNova.exe Hotfix 7 and GTZW Hotfix 5
Duplication option for updating existing Unit field Override Length via the ImportExportCSV now able to be the single option set to True
Life Time Warranty column in the Units grid now correctly uses the localization from LT_Unit_Label_OverrideLifeTime instead of LT_UnitModel_Label_LifeTimeWarranty
The warranty Override Length column in the Units grid now correctly uses the localization from LT_Unit_Label_OverrideLength instead of LT_UnitModel_Label_WarrantyLength
Warranty Terms column in the Units grid now correctly uses the localization from LT_Unit_Label_OverrideWarrantyTerms instead of LT_UnitModel_Label_WarrantyTerms
Note ** if you have created Unit grid report templates that used the previous UnitModel datafields, you will need to edit to use the new Unit labels
A negative number can now be entered in the Contract entry screen Discount % field. This is useful if instead of a discount applied, you want a markup applied.
Now if have deleted a client record, but that client was referenced in the Notifications Log, AyaNova will no longer error ClientPickList: ID not found: Instead, the client will be listed in the Notifications Log grid under the column of whom sent to as DELETED CLIENT
MBI login screen now displays version number 7.0.4.0 correctly
Change in how grids display text fields to prevent error message “Object reference not set to an instance of an object” that may occur if one or more of the text columns has non-text characters in it
April 27 2011 Unit importexportCSV utility now includes ability to import Warranty Field if needed.
April 20 2011 7.0.4.0 AyaNova.exe HotFix 6 (see instructions in separate post in this thread on how to apply if require these fixes)
Resolves issue where Schedule screen not automatically displaying newly saved Schedule Markers or scheduled workorder items unless Refresh menu option was selected.
Resolves issue where Schedule screen not automatically displaying selected Scheduleable User Group unless Refresh menu option was selected
Further work on Invoke or BeginInvoke error If this error message still occurs, please email support@ayanova.com that it has with copy of your ayalog.txt, version including HotFix # and what operating system in use
April 20 2011 Client importexportCSV utility now includes ability to import Region, Client Group and Dispatch Zone if needed.
April 12 2011 7.0.4.0 GZTW.AyaNova.BLL.dll HotFix 4 (see instructions in separate post in this thread on how to apply if require this improvement)
Provides additional column “Model Number” in the Units grid so can filter aphanumerically by model number not just model name as with the current “Unit Model” column in that grid
April 7 2011 7.0.4.0 AyaNova.exe HotFix 5 (see instructions in separate post in this thread on how to apply if require this fix)
Resolves issue where receive Error: “An error occurred while parsing EntityName” while filtering or sorting a grid under certain circumstances caused by the .net 4 DataSet.ReadXml() method
April 6 2011 7.0.4.0 HotFix (see instructions in separate post in this thread on how to apply if require this fix)
Resolves issue where Firebird BLOB fields (i.e. large memo fields such as Service Notes in the workorder entry screen, General Notes in the Client entry screen, etc) does not retrieve unicode text
April 5 2011 7.0.4.0 HotFix (see instructions in separate post in this thread on how to apply if require this fix)
Resolves issue where click on displayed Last Closed Service WO in the Unit’s grid, but the workorder opened is actually the last closed workorder for that client, not for that unit.
March 31 2011 7.0.4.0 HotFix (see instructions in separate post on how to apply if require this fix)
Resolves issue with the Schedule screen where if you have selected 3 or more weeks via the Date Navigator on the left, that when you scroll using the Schedule screen’s scroll bar on the right, that the scheduled items now correctly refresh and are accessible as you scroll to new dates.
Also note, if have selected 3 or more weeks via the Date Navigator on the left, and scrolling using the Schedule screen’s scroll bar on the right, do have your Date Navigator set to show at least two months. This is so that when you scroll, the Schedule screen will be able to show scheduled items in all weeks.
March 25 2011 7.0.4.0 HotFix (see instructions in separate post on how to apply if require this improvement)
Feature improvement that Preventive Maintenance Templates display for selection with Template description first, then PM Template # when creating a new PM
This makes it easier to select as you can start typing in the description and “jump” to the PM Template want to select, as may not know the PM Template number, but know the Description.
March 24 2011 CEImport utility replacement
Feature improvement - Now when the CE import is running, rather then just giving an error that could not import because hit a workorder that has an issue of some kind, the import will just list the workorder # it can not import and continue on.
This way, especially with a large long import, you don’t have to try to identify which workorder # has the problem, nor start all over again. The workorder just will not be imported.
Maintenance update 7.0.4.0 released March 17 2011
Refer to the AyaNova 7.0.4.0 Maintenance Update Steps forum post in this forum section
AyaNova Issues Resolved:
[ul]
[li]
[/li][li]Resolved memory errors such as Timeout error, Exception of type ‘System.OutOfMemoryException’ was thrown error, and A generic error occurred in GDI+ due to empty signature field in service grids consuming memory
[/li][li]Added keyboard combination CTRL-ALT-e for those that would like to see allocated memory freed up even though will do so automatically when needed elsewhere
[/li][li](was QuickFix) Date fields in the entry screens would display in US format even though computer’s regional settings set to a different country
[/li][li](was QuickFix)If printing a detailed type report template from the Purchase Order grid, all PO’s will display in your report even if have filtered to show only specific PO’s
[/li][/ul]
ExportToXLS Issue Resolved:
[ul]
[li]Resolved error System.Byte[] is not a supported cell value type that would occur if ran ExportToXLS utility from the Service Workorders grid
[/li][/ul]
WBI Issues Resolved:
[ul]
[li]Workorder hyperlink in Part request grid now correctly opens linked workorder entry screen
[/li][li]Users Default Warehouse set in their entry screen now is automatically selected when selecting part in workorder when logged in via WBI
[/li][/ul]
CASE 1387 ERROR message - If you receive the rare occurrence of the error CASE 1387 ERROR: AyaBiz Utils->Right - RootObject rights being checked is Workorder! using AyaNova 7.2, update to the latest AyaNova version.
Development had back with the initial 7.0 release added code to handle some legacy data that referred to workorder object instead of the specific type of workorder and could cause a potential rights problem.This code accidentally was removed from the 7.2 build so the patch puts it back in as it should have been to resolve those rare occurrences where this error occurs.
WBI 7.2 HotFix 1 - resolves cosmetic issue where the scheduleable user’s name that is displayed via WBI continues to show the user’s name of whoever first logged in via WBI.
QuickFix release of setup files January 29 2012
ToMSSQL (for migrating from stand-alone or network Firebird to SQL) will now reset invalid dates to 01/01/1966 so can be accepted by a SQL database
7.2.0.0 setup files released January 20 2012
NEW FEATURE Dashboard - navigation pane area where can now easily see at a glance overdue; scheduled; billable hours for current day, week, month and year; memos; and upcoming schedule markers and followups.
NEW FEATURE Show all… from the client entry screen - now quickly bring up all service workorders, quotes, PM’s and units for that client.
NEW FEATURE Show all… from the unit entry screen - now quickly bring up all service workorders, quotes, PM’s for that unit.
NEW FEATURE Show all… from the service workorder - entry screen now quickly bring up all service workorders, quotes, PM’s for that client of that workorder.
NEW FEATURE Localize “on the fly” - when logged in as the AyaNova Administrator, easily localize the text of labels displayed in that entry screen viewing FROM that entry screen. So quick!
Menu options with no data yet entered show grayed with dark line to indicate no data within (was previusly showing with light white line which was not noticeable for majority of users). For example, if no labor records within a workorder item, the Labor subsection icon within the service workorder will show grayed with a line through it so you know without having to check that there are no labor records as of yet.
License menu option under main Help now accessible even if not logged in as AyaNova Administrator, with a popup reminder need to be logged in as the AyaNova Administrator if wish to apply new license or erase database.
Not assigned column in graphical Schedule screen now display text as per the localized key Dashboard.Label.NotAssigned instead of “-”
Splash screen font of start up logo is blue for 7.2.0.0 onwards
Font used within the AyaNova user interface changed to the recommended modern Segoe UI font for utmost readability.
AyaNova 7.2.0.0 HotFix 2 Fixes released October 31 2012
FIX will no longer receive multiple email notifications if subscribed to Workorder ? ?Status? changed (if a user) or WO Status changed (if a client) and had made mulitple edits within the workorder that included editing the Workorder Status but only used the Save menu option.
FIX Workorder Status will now display correct workorder status name instead of GUID number when workorder is set to Closed, and you have a specific workorder status set in Global Settings for Workorder closed status
FIX if create a new client, create a new workorder and start typing in a unit’s serial number in the Unit field even though no unit record for this client has been entered into AyaNova, will no longer receive “Specified cast is not valid.” error. Instead, will remain within the Unit selection field until select the “-” which signifies no unit selected, and click on the Unit jump button to create the new unit so that it can be selected.
AyaNova 7.2.0.0 HotFix 1 Fixes released April 27 2012
FIX If attempt to delete a locale that is assigned to any users, will now receive a message identifying this if attempt to delete.
FIX Maximum embedded file size can now be edited to less than 50MB.
FIX If a workorder status is set to inactive, will now still show its name in the Workorder Status field in the workorder as was selected previous to setting to inactive, instead of showing an internal GUID.
FIX Automatic Client notification for Quote Status Changed, will now attach a PDF file with the date and time when sent instead of a file labeled workorder.pdf
FIX Scheduled user subscribed to Workorder Item Scheduled User (created/updated) now will only receive notification in regards to workorders. Will no longer receive notification if scheduled user is selected in a new or updated quote or PM.
FIX A PO with two different parts ordered, only quantity of one each, that has been partially received with one of the parts received and the other still on order, will now correctly remove the ordered non-received single part from a PO if have forced a Close
AyaNova 7.2.0.0 **GTZW.AyaNova.BLL.dll Hotfix 8 Fix released April 19 2013
FIX for QBI and for PTI resolves error “ImportToAyaNova error: Exception has been thrown by the target of an invocation.” when attempting to Auto-link or import or manually map/link
Issue was due to mappings from previous QuickBooks or Peachtree databases were not completely cleared out of the database before importing with a new accounting database
AyaNova 7.2.0.0 **AyaNova.exe Hotfix 8 Fix released April 9 2013
FIX for AyaNova 7 resolves error “Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index” that was occuring when embedding images in a wiki page
AyaNova 7.2.0.0 **BLL Hotfix 7 Fix released April 5 2013
FIX for AyaNova 7 Futher fix to BLL Hotfix 6 released April 3 2013
When a PO is forceably set to Closed - Partially Received that has part requests from specific workorder, the specific workorder part request will be updated so that the Qty ordered equals the Qty received so that the service workorder can be set to Service Completed.
NOTE: if had set the PO to Closed - Partially Received before applying this fix, you MUST change the status of the PO that was made with the part requests back to On Order - partially received, exit to save, and then open again to change the status to Closed - Partially Received to apply the correct changes to the service workorder so that it can be set to Service Completed.
AyaNova 7.2.0.0 **BLL Hotfix 6 Fixes & New Feature released April 3 2013
NEW FEATURE for AyaNova PTI PTI now compatible with Sage 50 2013 US
FIX for AyaNova 7 Resolved issue where would get the error message “Error: User is not authorized to change a Purchase Order Item or the object or field being changed currently is read only” when attempt to change the status to Closed - Partially Received of a PO that was created based on part requests from workorder(s)
FIX for AyaNova MBI 7 Resolved issue where inactive statuses would still show for selection via MBI only
AyaNova 7.2.0.0 HotFix 7 Fixes & New Feature released March 12 2013
FIX for AyaNova The Name column for Custom Fields in a workorder item (whether for a workorder quote or pm) will now automatically adjust its width to display all text. No need for the end user to attempt to adjust or save a specfic width.
NEW FEATURE for AyaNova AGE column now available for the Service Workorders grid which is caculated as a) if Service Completed is NOT checkmarked, then the difference in days between the service workorder’s Created Date (see the Record History menu option) and today’s date and time or b) if Service Completed is checkmarked, then the difference in days between the service workorder’s Created Date (see the Record History menu option) and the Last Modified Date & Time (see the Record History menu option)
****To set this new column to display, see as per http://www.ayanova.com/AyaNova7webHelp/setting_what_columns_display_i.htm
****This field is availble for reporting off of directly via a Service Workorder summary type report template only
AyaNova 7.2.0.0 HotFix 6 Fixes released Feb 18 2013
FIX for stand-alone use AyaNova Lite and/or AyaNova resolves issue where in some instances stand-alone AyaNova or AyaNova Lite were experiencing the program “freezing” due to the stand-alone generator attempting to make a Notifications connection in preparation for notifications.
Preventative fix for all configurations network or standalone If Use Notifications is set to False, both GenProcessClientNotifications (client notifications) and GenProcessDeliveries (user notifications) will exit early without doing any processing at all. And if Use Notifications is set to True but there are no notifications for either client or user to send, both processes will also exit early without probing the SMTP server.
AyaNova 7.2.0.0 HotFix 5 Fixes released Feb 15 2013
FIX Wikipages entered URL’s and email addresses now will display as a hyperlink
FIX Wikipages entered URL’s no longer having last character cut off
Fix Security group setting of Read Only for Object.WorkorderItem will now correctly limit read only access for all subsections including Unit, Outside Service, Tasks, and Custom Fields as well as Scheduled users, Parts, Labor, Travel, Misc Exp. No selection or changes will now be available if this is set for the security group. Same fix applies to WBI & MBI.
Fix Security group setting of Read Only for Object.WorkorderItemUnit will now correctly limit read only access for the Unit subsection. No selection or changes will now be available if this is set for the security group. Same fix applies to WBI & MBI.
AyaNova 7.2.0.0 HotFix 3 Fixes released January 21 2013
FIX for AyaNova Lite Now will be able to set Goods Only example tax code to inactive if using AyaNova Lite.
FIX for AyaNova & AyaNova Lite Memo grid will now automatically refresh when you delete a memo record, removing that memo record from the grid list.
FIX for AyaNova & AyaNova Lite Fix for Firebird databases (stand-alone or networked) to check case when checking if entering duplicate client name, part number or unit serial number as per topic SOLUTION-duplicate-notice-NOT-popping-up-when-entering-with-different-case
FIX for AyaNova AyaNova will now no longer allow a user to change the warehouse in a PO Receipt to receive to a different warehouse than from the warehouse originally was ordered for. This is to prevent invalid On Hand and On Order totals which are warehouse dependant. If you have an existing issue with this, do contact support BEFORE you apply this update so that we can provide you with the steps to undo your incorrect totals.
FIX for AyaNova Part Requests menu option in a Purchase Order will now show all part requests even if the Vendor selected is EITHER the Wholesaler or the Alternative Wholesaler
FIX for AyaNova Label for client selection window when creating new workorder via the Dashboard has now been correctly localized to obtain from the O.WorkorderServiceTemplate rather than from O.Region (was showing label as Region when should have been labeled Service Template)
FIX for ImportExportCSV Duplicate option Now when updating existing parts or units using the Duplicate option, the import success popup will now identify the number of existing parts or units updated as well as new parts or units imported. Previously was only doing so if at least one Client Duplicate option was set to TRUE.
AyaNova 7.2.0.0 Hotfix 9 (AyaNova.exe & GTZW.AyaNova.BLL.dll ) released August 22 2013
**NEW FEATURE for AyaNova ** Purchase Orders set to Closed now able to have their Custom fields edited for entering details about the PO after closed such as shipping costs, etc.
FIX for AyaNova User column in Travel grid in Service, Quotes and Preventative Maintenance navigation pane now filterable
FIX for AyaNova An locale file imported from an older version of AyaNova will now be compared against the present default non-edtiable English locale - if a key is missing in the older locale it will now be added to prevent the issue outlined in topic Known-Issue-with-exporting-importing-locale-(your-language-file)
WBI 7.2.0.0 Hotfix 3 released August 22 2013
FIX for WBI Part Requests grid via WBI menu no longer has New… buttom which had no function
FIX for WBI Default size of the large text fields Service Notes in a workorder item and Service Details in a Labor record is now 140 columns by 30 rows (used to be 22 columns by 10 rows). Now easier to enter in a lot of text and still be able to read as you type without having to scroll
FIX for WBI If using Chrome and have adjusted size of the large text fields Service Notes in a workorder item and Service Details in a Labor record, the formatting to show a carriage return when viewing these fields for editing will be maintained.
AyaNova 7.2.0.0 GTZW.AyaNova.BLL.dll Hotfix 10 released Sept 23 2013
FIX for AyaNova signature for devices/browsers that save x y coordinates as fractions fix for issue posted in topic RESOLVED-Input-string-was-not-in-a-correct-format-error-due-to-saved-Signature-format
AyaNova 7.2.0.0 GTZW.AyaNova.BLL.dll Hotfix 11 released March 31 2014
**FIX for issue whereby filtering on a text field that includes an & would not return correct results as per topic Resolved-issue-filtering-text-field-that-has-an-ampersand-amp-as-text
WBI 7.2.0.0 GTZW.AyaNovWBI.BLL.dll Hotfix 4 released June 14 2014
**FIX for issue so that when using iframes, login via client or head office account also results in the web page expanding as normal - see post Example-of-using-iframe-with-WBI-login too
AyaNova 7.2.0.0 GTZW.AyaNova.BLL.dll Hotfix 12 released Sept 05 2014
**FIX for issue where PM’s Next Service Date is not saved based on the Generate Time Span resulting in repeated generation of a new workorder for this PM.
See also topic RESOLVED-Workorders-repeatedly-generated-every-5-minutes-from-same-PM
WBI 7.2.0.0 GTZW.AyaNovWBI.BLL.dll Hotfix 5 released May 13 2015
**FIX for issue where Request Date column not showing in Workorder Items grid in a service workorder when logged in via WBI
AyaNova 7.3.0.0 October 18 2015
**CHANGE: Latest Dataportal web.config installed file contains additional lines to ensure users via dataportal connection can upload Wikifiles
**CHANGE: When an active scheduleable user is set inactive and saved successfully, an automatic scan will be triggered for Follow Ups that have a stop date that is later than the current moment and compiles them into a list and sends it via memo to the Administrator account
**CHANGE: Now when a Quantity # is entered first instead of selecting Part first in a Parts record in a service workorder, the Quantity now is able to be compared against the OnHand to determine if there should be a Parts Request or not.
**CHANGE: In the unlikely event that an exception occurs when the PM source workorder is attempted to be saved after the service wo is generated, AyaNova will automatically delete the service wo just created, generate an error message and will send details to the administrator account via memo. This prevents infinite workorders being generated.
**CHANGE: Now now longer possible to save a PO with a negative Quantity Ordered. This is to prevent PO issues, as a PO is expected to be used for ordering in, not returning.
**CHANGE: Dates in service workorder grid columns will now show text if that is your computer’s Regional settings (i.e. if your Regional is set to dd-mmm-yyyy will now show 12-Oct-2015 in the Service Workorder’s grid Service Date column field)
**CHANGE: Can now Move a Quote’s woitem to another Quote OR workorder for the same client. Can now Copy a Quote’s woitem to another Quote OR another workorder for the same client. Not just to another workorder.
**CHANGE: Two additional Part Display Formats added for selection in your Global Settings.
**CHANGE: The Postal Code from the client’s physical address now available for display on the Service Workorder grid and is available for display in Summary type report templates from this grid too.
**FIX: Inactive parts will no longer show for selection in a PO.
**FIX: Resolved issue that if an initial Notification Subscription with a workorder status selected gets deleted, AyaNova will now no longer cause other workorder status related notification subscriptions for that user to fail.
**FIX: Fixed API bug preventing a dynamic connection setting from being used
**FIX: In biz object library, CSTR list is now filterable by serial number of the unit
**FIX: Resolved input string was not in correct format ? error that occurs when viewing grid of workorders when device being used reports and enters internally a number NaN outside the normal co-ordinates expected by the signature script
**FIX: Resolved error Arithmetic overflow error converting expression to data type int.? that shows when attempting to view Files in Database if have a very large number of files of substantial size
**FIX: Resolved issue where in some circumstances the last letter of first line of message body in a clients Notification email message cuts off in Subject line
**FIX: Part Adjustment form’s column order now saveable for the next time user views same form
**FIX: Memo TO: now correctly does not include client and ho user accounts
**FIX: Travel’s Travel Details field is not a memo field and will now correctly prevent entry of more than 255 characters.
**FIX: Resolved issue whereby a Task Group delete causes GUIDID to then show in selection. Now no longer shows preselected the Task Group record that was edited.
WBI 7.3.0.0 October 18 2015
**FIX:Resolved and prevents error "Object reference not set to an instance of an object"when creating new wo via Schedule when double-click on day instead of selecting +New menu option
**FIX: Removed part warehouse grid field DefaultWarehouseID from showing
MBI 7.3.0.0 October 18 2015
**FIX: Resolved issue when attempting to add users via TO: when creating Memo via MBI
**FIX: Resolved issue in some circumstances that prevented ability to create new Memo via MBI
.
AyaNova 7.3.1.0 released Nov 18 2015
FIXEDInactive users will now no longer display as select-able to send an internal memo too
FIXEDResolved error The multi-part identifier “AADDRESS.APOSTAL” could not be bound that occurs when selecting to print any detailed report template from the Service Workorders grid if the column Postal/Zip is enabled to show in this grid.
RI 7.3.1.0 released Nov 18 2015
CHANGE If you encounter a web browser that does not provide the ability to fully edit date/time, uncheck the new feature Browser Settings as per http://www.ayanova.com/AyaNova7webHelp/index.html?ri-browser-settings-.htm
FIXEDResolution of incorrect link automatically created within a Quote’s wiki page that results in error “The resource cannot be found” if clicked when logged in via RI.
.
AyaNova 7.3.2.0 released Nov 25 2015
FIXED Removed issues that began as of 7.3.0 that would ask the end user if they wished to create a Part Request when adding a part via a Quote or PM. A part request is only to be created when adding a part to a service workorder when there is no quantity in stock.
FIXEDIssue introduced in 7.3.0.0 that even when Use Inventory = False, when adding a part to a service workorder, AyaNova was asking if enduser would like to create a part request.
AyaNova RI (responsive interface) 7.3.2.0 released Dec 14 2015
FIXED Embedded file link selection now results in download of file when selected
FIXEDDelete of embedded file now possible
AyaNova network Generator 7.3.1.0 released Jan 19 2016
NEW FEATURE* network Generator service will now display the registered name of the database connected to.
This is to facilitate hosting companies that host multiple AyaNova databases on a single computer, so that if an issue with network Generator can easily identify which database the issue is with.
AyaNova WBI (web browser interface) 7.3.1.0 released Jan 27 2016
FIXED Client Notes subgrid Notes column now displays with same formatting (carriage returns etc) as do via desktop AyaNova and via RI.
AyaNova RI (responsive interface) 7.3.3.0 released Jan 27 2016
FEATURE CHANGE Users last view showing either Month, Week or Day in Schedule is now saved in browsers localStorage object which is persisted in the browser between sessions so that when using that browser on that device, your Month/Week/Day selection when last logged in will persist for you.
FEATURE CHANGE Selection buttons (i.e. Save, Back, More…) are now full column width resulting in easier selection via tablet and small screen phone
FIXED Inactive parts no longer show for selection in a workorder via RI
FIXED Inactive users no longer show for selection in a workorder via RI
FIXED Inactive unit no longer shows for selection in a workorder via RI
FIXED When Use Inventory = False, RI no longer results in error attempting to view parts in workorders
FIXED Error no longer occurs deleting a memo via RI
AyaNova 7.3.(patch 3) released Feb 23 2016
NEW FEATURE Optional add-on PTI now compatible with US Sage 50 2016
FIXED Search Database will now return search results when search includes an apostrophe (as internally the apostrophe is actually stripped out)
FEATURE CHANGE Added new pre-set date filters for date columns in the main grids
[ul]
[li][PAST] Jan 2 1753 up to Now (FYI 1753 is minimum year in both MS SQL and Firebird)[/li][li][FUTURE] From Now to forever[/li][li][LASTYEAR] From zero hour Jan 1 last year to zero hour Jan 1 this year[/li][li][THISYEAR]From zero hour january 1 this year to zero hour Jan 1 next year[/li][li][INTHELAST3MONTHS](Now - 3 months) up to Now[/li][li][INTHELAST6MONTHS](Now - 6 months) up to Now[/li][li][INTHELASTYEAR] (Now - 365 days) up to Now)[/li][/ul]
FIXED The quantity of parts entered into a quote template or PM template, will now be transferred to the quote/pm created from it.
AyaNova RI (responsive interface) 7.3.4.0 released Feb 23 2016
NEW FEATURE Client RI now bundled with RI
FEATURE CHANGE Added new pre-set date filters for date fields in Filtered area
FEATURE CHANGE WorkorderItemPart.Label.QuantityReserved in a service workorder generated from a quote now displays in red font as a helpful reminder which is quoted and which is actual
FEATURE CHANGE Numerous performance improvements and speed optimization
FIXED Search Database will now return search results when search includes an apostrophe (as internally the apostrophe is actually stripped out)
AyaNova WBI (responsive interface) 7.3.3.0 released Feb 23 2016
FEATURE CHANGE Added new pre-set date filters for date columns in the main grids
FIXED Search Database will now return search results when search includes an apostrophe (as internally the apostrophe is actually stripped out)
AyaNova RI 7.3.5 released March 7 2016
FIXED Selecting a Status in a CSR is required. Have edited the CSR form so that one of the three options must be selected