Bug Fixes and Enhancements

• • Release 1
  • Release 2
  • Release 3
  • Release 4
  • Release 5
  • Release 6
  • Release 7
  • Release 8
  • Release 9
  • Release 10
  • Release 11
  • Release 12
  • Release 13
  • Release 16
  • Release 18

Release 1

• Expression Builder Stock & Valuation Functions: Integrated GetCostRate() and additional financial/inventory calculation functions into the Expression Builder for web use.
  • GetCostRate(ItemId:numeric, DocDate:Date, IssueQty:numeric, VMethod:Char, PLockId:String, CompanyId:numeric, BranchId:numeric, BatchId:numeric)
  • GetClosingStock(ItemId:numeric, DocDate:Date, VMethod:Char, PLockId:String, CompanyId:numeric, BranchId:numeric, BatchId:numeric)
  • DoMRP(SDate, EDate:String)
  • CheckStock(ItemId, OldItemId, DocDate, OldDocDate, PlusOrMinus, Qty, OldQty)
  • GetStockValue(ItemId:numeric, DocDate:Date, IssueQty:numeric, VMethod:Char)
• Form Field Visual Interface Standardizations: Updated and aligned the UI layout for special and basic input fields across development environments, excluding component fields.

Release 2

• Tabbed DC Design Mode Layout: Resolved layout rendering and structural alignment issues occurring within Design Mode for Tabbed Data Components (DCs).
• GenMap Grid-to-Grid Field Mapping Order: Fixed a structure save issue in GenMap where target field ordering saved in the web environment differed from desktop definitions, resolving grid-to-grid mapping execution errors (e.g., “row 2: either debit or credit should be entered”) on data import screens.

Release 3

• Alpha and Alphanumeric Double-Space Validation: Added validation rules for isalpha and isalphanumeric field patterns to treat consecutive double spaces as invalid special characters and prevent record saving.
• Iview Developer Eval Function Validation: Resolved an “Invalid Input detected” security/validation error encountered while attempting to define Eval functions within the Iview developer studio.
• Axprops Mail Configuration Persistence: Fixed a database synchronization defect where mail configuration entries were erased from the axprops table whenever Axvariables were created or updated.

Release 4

• DevStudio Event Script Validation for InitGrid: Resolved an issue where saving the InitGrid function within Before Save or After Save Transaction events threw an “InitGrid is not allowed in selected event” error.
• SQL Editor Data Type Schema Alignment: Fixed a query generation defect where fields converted from character to numeric data types were still evaluated as character types in SQL Editor, resolving “operator does not exist: numeric = character varying” execution errors.
• Normalized Dropdown Field Data Type Conversion: Resolved an issue where enabling the “Normalized Field” property (source key = true) on standard dropdown fields failed to update the backend database schema to numeric, leaving it as character.
• Arrange Menu Visibility Persistence: Fixed an issue where converted forms automatically defaulted to hidden mode in the Arrange Menu upon saving in DevSite, requiring manual unhiding to remain visible at runtime.
• Data Component Table & Field Re-creation: Resolved database schema generation issues where dropping DC tables from the backend prevented tables from being re-created during “Save Structure” or new fields from being added to manually re-created tables.
• Developer Option File Type Selection: Fixed submission failures when selecting all file formats in the “Upload file types” developer option using the Select All control.
• Developer Options Tooltip Correction: Corrected tooltip text for the New button within constant, variable, and application parameter screens, which incorrectly displayed “New PrintDefinition.”
• Upload File Types Display Value: Standardized the display value of the “Upload file types” developer option to render as “All” whenever more than 7 file formats are selected.
• Script Field Suggestive List Overlap: Fixed UI overlay defects in DevSite script fields where suggestive autocomplete lists overlapped adjacent input elements.
• Script Field Suggestive List Dismissal: Corrected event handling in DevSite script fields so suggestive autocomplete dropdowns dismiss properly upon pressing ESC or clicking outside the field.
• Grid DC Numeric Field Total Footers: Introduced a new Display Total checkbox property for numeric fields in Grid DCs (defaults to false). When enabled, the calculated total automatically displays in the grid footer at runtime.
• Form Control Script Definition Filtering: Enhanced the Script Definition interface to filter and display form control functions exclusively when the Form Control checkbox is selected during definition.
• Table Field Database Procedure Execution: Resolved execution failures where database procedures attached to table-type fields failed to trigger within the Axpert Developer Site.

Release 5

• Save Structure Data Integrity & Schema Constraints: Resolved critical schema modification and data corruption issues in Axpert 11.3 Save Structure.
  • Fixed an issue where normalized field values were wiped or reset to zero upon saving the structure.
  • Enforced strict database safeguards preventing conversions from Normalized to De-Normalized fields if the transaction table already contains normalized data.
  • Enforced safeguards on PostgreSQL preventing data width reductions or data type modifications when the target transaction table contains active data.
• Iview Parameter Table Field Accessibility: Fixed an issue where the Params Table Field rendered as disabled within Iview definitions.
• Param Iview Numeric & Date Column Creation: Resolved creation failures when attempting to build Parameter Iviews containing numeric and date data columns.
• Iview Sub-Total Advanced Settings: Enhanced Iview definitions by introducing dedicated Advanced Settings for configuring Iview sub-totals.

Release 6

• DevSite SQL Editor Parameter Display: Fixed an issue in the Utility SQL Editor where running queries with parameters displayed a blank “Define Parameters” window.
• DevSite Query Parameter Type Error: Resolved an Oracle DBX driver exception (ORA-01036: illegal variable name/number / TDBXTypes.UNKNOWN data type) when running parameterized queries across TStructs, Iviews, or Cards.
• DevSite Iview Hyperlink Field Mapping: Fixed a validation error (“Row 1 is empty. Please enter data.”) when attempting to add field mappings in the Iview Hyperlink popup screen.
• Normalized Data Schema Lockout: Restricted query modifications to prevent converting normalized fields back to denormalized when the underlying transaction table already contains normalized data.
• Structure Save File Lock Handling: Fixed intermittent structure save failures caused by background process file locks (I/O error 103 / File being accessed by another process).

Release 7

• Definition-Level Column Freezing for IViews and ListViews: Introduced a column-level Freeze Column property in the definition interface alongside the existing runtime freeze controls. Solution developers can now define sticky/frozen columns directly during design time to enforce consistent layouts based on business requirements.
• Flexible IView Row Option Positioning & Custom HTML Definition: Added structural controls to position the axrow option button within any column position in an IView report, including placement between data columns.
  • Column-Level Hyperlink Setup: Developer site now features a hyperlink at the column definition level that opens a Row Option configuration form. Developers can supply custom HTML definitions to render tailored row option controls at runtime.
• Custom Financial Formatting for Negative Numeric Values: Introduced a new column-level property allowing negative values to display in standard financial formats.
  • Credit/Debit Suffixes: Native values suffixed with Cr or Dr (e.g., 1,000 Cr, 500 Dr).
  • Accounting Brackets: Enclosed in parentheses (e.g., (1,000)).
• API URL Execution via Run Schema (MOE Select from API): Updated MOE Select from API execution logic to fetch API URLs dynamically from the Run Schema rather than hardcoded entries in the Structure XML.
  • Migration Note: Existing structures must be resaved in DevSite to source the API URL from the Run Schema. If unsaved, legacy structures will continue to fall back to the URL stored within the Structure XML.

Release 8

• IView / ListView Pagination Record Fetching: Resolved an issue in record listings (such as Employee Listing) where the pagination footer correctly displayed the total record count, but the table grid failed to render the underlying rows.
• TStruct View Column Type Alteration Error: Fixed a DevSite schema update issue where saving a TStruct linked to a database view triggered the error: “cannot alter the type of a column used by a view or rule”.
• AxRelations Table Master Data Synchronization & De-duplication:
  • Duplicate Entry Prevention: Fixed duplicate record creation during AxRelations table persistence operations.
  • Master Form & Master Field SQL Updates: Handled From SQL field updates to correctly validate and align updates based on the designated master form and master field configurations.

Release 9

• Runtime Data Import SQL Editor JSON Parsing Fix: Fixed an issue where executing SQL queries against tables that recently received runtime imported data caused a JSON parsing error in the DevSite SQL Editor (“Uncaught SyntaxError: Unexpected token ‘A’, … { ‘error’: ‘An invalid … is not valid JSON”).
• Developer Site Cross-Schema Table Access: Resolved a PostgreSQL table relation error (“relation ‘Table name’ does not exist”) when attempting to access Global Schema tables from within a Client Schema on the Developer Site.
• Online TStruct & IView Definition Save-As Safeguard:
  • Hidden the Save As button in DevSite for online TStruct and IView definitions to maintain structural integrity.
  • Guideline: Saving structures as new definitions must be performed via the Axpert Desktop Executable and subsequently converted using the ‘Go Online’ tool for valid conversion use cases.
• Toolbar Default Button Removal Persistence: Fixed an issue where default runtime toolbar buttons remained visible even after a developer explicitly removed all default buttons from the toolbar configuration in DevSite.
• Arrange Menu Single-Click Save Fix: Resolved an issue in the Arrange Menu where layout and hierarchy changes failed to persist on the first save attempt, requiring users to click the save button multiple times.
• Arrange Menu Icon Selection Modifier: Fixed an issue in the Arrange Menu modal where users were unable to modify or reselect menu icons within the active editing window.

Release 10

• Global Schema Table Access in Database Calls: Fixed an issue where Global Schema tables were inaccessible during standard database operations within application (app) and definition (def) schemas, raising “relation table_name does not exist” errors.
• Global Schema Support for Multi-Select Fields: Resolved database resolution failures when referencing Global Schema tables within Multi-Select dropdown and lookup fields.
• Developer Studio AXToolbar Table Persistence: Fixed a form save issue in Developer Studio where runtime updates to the AXToolbar table failed due to SQL syntax conflicts involving the reserved keyword key.
• TStruct Structure Save Failure on ListView Enablement: Resolved a DevMode bug where enabling the ListView property on a form prevented the structure from saving successfully and suppressed the “Structure Saved” confirmation notification.
• ListView Property Structure Lock Fix: Fixed an issue causing form structure saving operations to fail or hang when updating ListView configurations across client environments.

Release 11

• Default Home Page Cards Configuration: Updated the default home page card settings to support Menu Options and Menu Folder choices.
  • Requirement: Only KPI cards can be set as home page cards in Axpert Developer card definitions.
  • Upgrade Note: Projects using existing home cards must re-save those cards after applying this patch.
• Dynamic DC Caption Script Function: Introduced the Form Control script function SetDCCaption() to dynamically change Data Control (DC) captions using form control events.
  • Syntax: SetDCCaption({dcName},{New Caption})
  • Example: SetDCCaption({dc1},{Test DC1}) or SetDCCaption({dc2},{Test DC2})
• Multi-Select Parameter Default Values (Task ID-011724): Resolved an issue in IView runtime where multiple default values were not displaying in Multi-Select parameters.
  • Configuration Rule: Multiple default values must be provided as a tilde (~) separated string in either default values or expressions.
  • Example: Expression set to {EMP-002~EMP-004} or Default Value set to EMP-002~EMP-004.
• Time Field Pattern Property for 24-Hour Format (Task ID-011700): Added the Pattern property field to Time Fields, allowing developers to configure and enforce 24-hour time formatting.
• Dropdown Value Spacing Alignment (Task ID-008465 / Task ID-010315): Fixed a visual layout issue where scrolling down in an open dropdown created unwanted blank space between the list values and the refresh action button.
• Form Properties Tab Duplicate Window Safeguard (Task ID-008465): Fixed tab management behavior to prevent the Form Properties tab from opening duplicate instances when it is already open.

Release 12

• Read-Only Mode Option for IView Hyperlinks & LoadFormAndData Script:
  • Introduced a new property in IView Hyperlink definitions titled “Open transaction in readonly mode” to specify whether target records load in Read-Only or Edit mode.
  • Updated the LoadFormAndData script function to accept a boolean parameter (t/f) controlling Read-Only vs. Edit mode during form launches.
  • Example: LoadFormAndData({tform},{username=:username},{d},{f},{t})
• Autocomplete Dropdown Performance Optimization: Resolved a performance degradation issue in Autocomplete dropdown controls (Select MOE fields) during continuous data entry within the same form session.
• Form Controls Script Field Cursor Visibility: Fixed an issue in DevSite where the text editing cursor became invisible inside script fields after checking the FormControls option.
• Configuration Property Save Error Fix: Fixed a validation error (“Property Code: value exceeds defined width”) that occurred while saving configuration properties.

Release 13

• Developer Site HTML Pages Loading Fix: Resolved an issue where created HTML pages failed to load in Developer Site after applying patch AD_R12.
• Data Source Query Parameter Popup Resolution: Fixed an issue in Data Source configuration where entering queries containing parameters rendered a blank Parameters table field popup.
• Developer Site Pages Load Error Resolution: Resolved runtime error messages triggered when attempting to load created HTML pages within Developer Site Pages.
• Read-Only Mode Option for IView Hyperlinks & LoadFormAndData Script:
  • Introduced a new property in IView Hyperlink definitions titled “Open transaction in readonly mode” to specify whether target records load in Read-Only or Edit mode.
  • Updated the LoadFormAndData script function to accept a boolean parameter (t/f) controlling Read-Only vs. Edit mode during form launches.
  • Example: LoadFormAndData({tform},{username=:username},{d},{f},{t})

Release 16

• Read-Only Mode Option for IView Hyperlinks & LoadFormAndData Script:
  • Introduced a new property in IView Hyperlink definitions titled “Open transaction in readonly mode” to specify whether target records load in Read-Only or Edit mode.
  • Updated the LoadFormAndData script function to accept a boolean parameter (t/f) controlling Read-Only vs. Edit mode during form launches.
  • Example: LoadFormAndData({tform},{username=:username},{d},{f},{t})
• Autocomplete Dropdown Performance Optimization: Resolved progressive performance degradation in Autocomplete controls (Select MOE fields) during high-volume continuous data entry within a single form session.
• Script Field Form Controls Focus Fix: Fixed a UI issue where the input cursor became invisible when selecting the Form Controls checkbox inside Script fields.
• Configuration Property Length Validation Fix: Resolved a “Property Code* : value exceeds defined width” validation error when saving Configuration Properties.

Release 18

• Developer Site HTML Pages Loading Fix: Resolved an issue where custom HTML pages failed to render after updating to the AD_R12 patch on developer sites.
• Data Source Parameter Mapping Popup Fix: Fixed an issue in Data Source definitions where entering parameterized SQL queries resulted in a blank Parameters table popup.
• Pages Module HTML Page Loading Exception: Resolved page load exceptions occurring when opening saved HTML pages within the Pages management interface.
• Read-Only Mode Option for IView Hyperlinks & LoadFormAndData Script:
  • Introduced a new property in IView Hyperlink definitions titled “Open transaction in readonly mode” to control whether target records load in Read-Only or Edit mode.
  • Updated the LoadFormAndData script function to accept an additional boolean parameter (t/f) specifying Read-Only vs. Edit mode during form launches.
  • Example: LoadFormAndData({tform},{username=:username},{d},{f},{t})