Velixo Classic v7 Release notes - Insider Channel
Created by Damien Zwillinger, Modified on Thu, 19 Oct 2023 at 03:25 PM by Pavel Kabir
This article lists out all Velixo Classic v7 releases of our Insider Channel, released in 2022/2023.
For earlier releases, please visit:
- Velixo Classic v6 Release notes - Insider Channel (released in 2021/2022)
- Velixo Classic v5 Release notes - Insider Channel (released prior to 2021)
TABLE OF CONTENTS
- Version 7.0.882.8446
- Version 7.0.876.58389
- Version 7.0.874.3531
- Version 7.0.728.12821
- Version 7.0.713.37741
- Version 7.0.707.37741
- Version 7.0.705.45132
- Version 7.0.668.8899
- Version 7.0.664.31051
- Version 7.0.592.6622
- Version 7.0.563.51093
- Version 7.0.561.22202
- Version 7.0.419.37606
- Version 7.0.407.35713
- Version 7.0.275.5309
- Version 7.0.258.19054
- Version 220.127.116.11953
- Version 7.0.209
- Version 18.104.22.168028
- Version 22.214.171.124912
- Fixed an issue where Velixo would not account for inactive companies' balances when the new argument UseMasterFinancialCalendar is set to TRUE in Velixo balance formulas (#2973)
- When UseMasterFinancialCalendar is set to FALSE or not used in Velixo balance formulas, the app would still incorrectly require the relevant financial periods to be set up in all companies. (#2973)
- Velixo returned an "Object reference not set..." error during refresh if the ERP tenant contained inactive companies with missing financial periods in its financial calendar. (#2969)
💡 If you have recently installed the update 7.0.849, please update to this version. It contains the same functionality, but avoids a breaking change related to the "master financial calendar" functionality that was present in 7.0.849.
- This is the first first version of Velixo that supports the upcoming ERP 2023R2 release. If you plan to upgrade your ERP system to a new version soon, make sure you update Velixo, too.
- Leverage the master financial calendar in GL and PM functions! This is immensely useful in multi-company consolidation scenarios, where different companies utilize different financial calendars or shifted financial years. To enable this feature, set the new UseMasterFinancialCalendarargument to TRUE in supporting Velixo functions. (#2884)
- ❗Attention: utilizing this functionality requires setting up new generic inquiries on your ERP site. If your site uses the Velixo customization package, the updated inquiries are shipped as part of our latest customization package.
- Revamped help & support experience under the "Support and Feedback" button: browse articles from our updated Help Centre or get in touch with our support team without leaving Excel. (#2933, #2954)
- Velixo now supports creating Generic Writeback worksheets with a large number of columns in the import scenario. Previously, it was not possible due to formula length limitations. (#2888)
- Improved error reporting for access rights errors on MYOB Advanced sites. (#2890)
- When navigating to Commitments from a PM drill-down worksheet, Velixo will now set the relevant cost code filter on the Acumatica screen. (#2892)
- Improved reliability of IntelliSense tooltips. (#2883)
- More detailed reporting on budget writeback progress. (#2907)
- When creating a new Generic Writeback worksheet, sometimes the list of import scenarios was not retrieved from the ERP system due to a race condition. (#2886)
Better error message when Excel cannot be launched by Velixo's command-line tool. (#2877)
Fixed a recent regression in the less commonly used LASTREFRESHDATE and LASTREFRESHBY functions (#2875)
A distribution list, when launched using the command line tool, could display #N/A errors in the resulting files in case the source workbook contained volatile functions like =TODAY() or =NOW(). (#2881)
Argument tooltip was not displaying for Velixo functions after a recent underlying library upgrade. (#2885)
Velixo users whose ERP system was in "single-tenant mode" (not supporting fully qualified OData URLs containing the tenant name) could not log in with an error: "Root element is missing" (#2872)
Fixed a regression that caused drilldown on cells referencing a dynamic array to fail. (#2871)
Velixo formulas will short-circuit and not attempt to evaluate in case on of the arguments supplied to a formula is an Excel error. This significantly improves calculation performance in error scenarios. (#2857)
Better resiliency in making web requests on low-core CPUs. (#2823)
Improved error message when Distribution List fails due to pivot table slicers containing unsupported symbols like "$". (#2829)
Velixo will now detect if you have specified any invalid values in a Velixo range expression, e.g. "CUSTOMER1;CUTOMER2" instead of "CUSTOMER1;CUSTOMER2". (#2842)
Note: this does not apply to wildcards and "range ranges" like "100:999", only to "explicit units" within a range expression.
Better drilldown performance on workbooks containing a lot of spill ranges. (#2846)
Better error message in WRITEBACKBUDGET when one of the required period amounts is left blank (probably due to an unintended extra comma in the formula). (#2848)
Velixo is now making a better effort to preserve value formatting after Copy without formulas, especially for number-like values formatted as text. (#2861)
Fixed an incorrect error message appearing randomly in the connection editor: "That doesn't look like a valid ERP website". (#2824)
Velixo could not detect whether single sign-on was available for a site when the user entered the tenant name with extra trailing spaces. (#2826)
0x800A03EC error occurred during Copy without Formulas whenever one of the values in a spilling range was longer than 255 characters. (#2835)
Excel could crash during opening when a file was split into the two-window mode. (#2838)
ExcelDNA error in ArrayResizer was observed by some users intermittently. (#2863)
Auto Hide Zero Rows did not properly re-triggering for rows that dynamically become blank depending on a formula. (#2865)
A minority of users observed Excel window becoming slow and laggy after a Velixo installation. We detected the problem in the underlying library and resolved it. (#2847)
Some JAMIS Prime users were not able to retrieve account balances using Velixo because their system was responding with an incorrect ERP version number. We worked around this issue. (#2868)
Fixed a situation where the Auto-Hide feature could leave some zero values when reapplied.
Fixed a race condition that could theoretically lead to inconsistent values when calculating reports with hundreds to thousands of Project balances.
Added a possibility to explicitly specify the maximum generic writeback chunk size to avoid accidentally splitting one document into many.
To leverage this functionality, use the ScreenSettings argument of the WRITEBACK() function, which replaces the old ScreenID argument.
Example argument value: "AR303000;BatchSize=999".
The default upload chunk size is 100 lines if you don't specify this parameter.
Drastically improved GL writeback performance for people using single sign-on. (#2816)
Significantly boosted the Budget writeback performance for people using username & password authentication, as long as Velixo's customization package is properly installed in the system.
More responsive operation cancellation for Writeback and Distribution. (#2668)
"GL writeback" template worksheets are now called "Journal Transaction" for clarity. (#2772)
Velixo will not fail anymore when the user specifies an invalid output parameter for generic WRITEBACK(). The upload itself will go through, but the output cell shall receive an error message.
A clearer error message during distribution when the user's auto filter only covers a part of a function's spilling range.
A clearer error message when a user tries to run a Distribution List for a hidden tab (#2774)
Copying without formulas:
When copying workbook without formulas, Velixo will now attempt to preserve leading zeroes in all-digits subaccounts like "100200" and financial periods like "012013". (#2819)
Improved handling of dashes in ERP tenant names.
It sometimes occurred to our clients that Microsoft Word automatically replaced dashes with em-dashes in the tenant name.
Velixo now takes care of converting them back to dashes so as to avoid unexpected sign-in errors.
Refresh & calculation:
Better error message produced when an entity configured for Smart Refresh returns a null or a non-timestamp/datetime value. (#2767)
Improved error messaging when an ERP data stream crashes midway while refreshing the data. (#2780)
Using Connection manager is now forbidden while calculations are in progress. (#2796)
Optimized away an unnecessary automatic refresh upon opening the file in case it contains Velixo's auto-hide ranges.
Velixo will now always evaluate the current cell during drill-down even if it contains functions that cannot be navigated for precedents. (#2792)
Due to a limitation in the ERP system, smart-refreshing the GL balances using dates instead of financial periods could miss transactions occurring within a certain day, after a new transaction was posted in the period of interest. (The issue was always fixable by a full refresh). (#2800)
Fixed a race condition that could theoretically lead to an erroneous zero value when calculating GL balances using dates instead of financial periods. In practice, we have never seen this. (#2803)
If a user entered a tenant name using an incorrect case, the error would not disappear even after they re-entered it with proper capitalization. (#2777)
In cases where the GL batch numbering sequence was configured to contain only digits, the user could not execute writeback in case the format of the Last Batch Number template cell was anything other than "Text". (#2782)
Added Commitments column to PM drilldown (#2761)
Significantly decreased network traffic consumption by leveraging OData gzip compression. (#2742)
Project revision is now a required field in forecast writeback (#2743)
Consistent telemetry with NX re: workbook name hashes, we can now cross-correlate data with NX properly in that regard (#2745)
Added telemetry for VELIXOVERSION function invocations. (#2757)
EXPANDPROJECTHISTORY now accounts for rows with negative amounts too (previously it included only positive ones, but in reality we just want "non-zero") (#2737)
EXPANDPROJECTHISTORY complained about missing revisions if there were no forecast revisions in Acumatica/MYOB (#2739)
Added a fixed ProgID to the Ribbon COM component (for NX purposes)
In case GL writeback fails after a partial upload, Velixo will delete the created batch (#2747) - previously it would leave it partially uploaded.
Hotfix for customization package for Acumatica 2023R1 where customization would not publish (regression in Acumatica) (#2749).
IntelliSense stability fixes, more reliable arguments pop-up. (#2751)
Any updates to Velixo user license will now propagate immediately after "clear local cache" without anyone having to restart Excel. Previously, a restart was needed. (#2753).
Fixed a rare case where:
when there was e.g. a lowercase "project forecast" worksheet in Excel,
and the user attempted to create a "New Writeback Worksheet" for project forecasts,
Velixo would not detect the existing worksheet name as it is lowercase,
would attempt to create a sheet with the same name without adding a numerical postfix (1) to it,
and therefore fail. (#2754)
For longer workbook names, it was not possible to add more than 9 writeback / drilldown worksheets to the workbook due to the name overflow. (#2755)
Fixed a performance problem when entire rows were selected and the user pressed "Writeback selected cells" (#2763)
It was possible to accidentally launch two parallel drilldown operations or other ribbon operations by rapid-clicking the button, which we suspect leads to potential inconsistencies (#2766)
An "object reference" error could be observed at start-up time by a subset of users.
❗Important (action may be required)
EXPANDPROJECTHISTORY now includes project forecast revisions column in the output. Use the ExpansionOrder parameter to exclude revisions if necessary. (#2664)
Velixo has a new look!
Brand-new ribbon icons, delivered as part of our unified experience across all the platforms supported by Velixo Reports and Velixo NX.
In Excel ribbon, instead of the ERP name (Acumatica / MYOB Advanced / CEGID etc.), you will now simply see "Velixo".
Significantly improved refresh speeds for reports that request balances by a specific date instead of a financial period. (#2645)
Improved reliability of large GL writebacks. (#2647)
Better user experience when your ERP single sign-on token expires: having previously just returned an error message, Velixo will now display the connection prompt. (#2642)
More responsive "Cancel" button during connection. (#2627)
Added support of BYROW() function being applied to Velixo writeback functions. (#2696)
Improved resulting file size for "Copy without all formulas" when the workbook contains spilling ranges. (#2715)
Generic Writeback and WRITEBACK() function:
Added support for special characters like "#" in import scenario column names. (#2653)
When passing arguments into a WRITEBACK function: if some data arguments are columns of the same height, and some are single cells or hard-coded constant, Velixo will now smartly duplicate these constants across all rows for your convenience. (#2621)
For example, in an invocation like WRITEBACK(..., B3#, "01-2020"), where B3# has 10 rows, "01-2020" will be treated as a column of 10 values of "01-2020".
This is convenient for the user when a particular value should be the same across every row.
Velixo will not try to process attachment columns of the import scenario unless the user explicitly uses that column in the writeback data. (#2655)
Improved handling of the situation when the import scenario in the ERP does not contain any columns. (#2659)
WRITEBACK will now produce an error message when one or more of the output cells reside on a protected worksheet. (#2734)
When distributing selected rows only, Velixo will only validate those, ignoring errors in rows that don't participate in the selection. (#2657)
Better detection of user-corrupted distribution list templates. (#2624)
In case a pivot table cannot be refreshed during a report distribution, Velixo will now include the table / worksheet name in the error message. (#2706)
Added support for handling pivot tables referring to entire columns on the worksheet. (#2710)
More meaningful error message when a user does not have access to a generic inquiry in the ERP. (#2623)
Improved detection of the 32/64 bitness of Microsoft Excel in Velixo's command line tool. (#2556)
Better error message for ACCOUNTS...WITHHISTORY functions when non-existent branch is specified. (#2555)
Velixo will now attempt to restore previous auto-filters after "Unhide All" is pressed. (#2662)
GIFILTER(..., "*") will now work even for non-string column types, which will allow any value for that column. (#2661)
All-space argument values are now treated the same as an empty string. (#2651)
Better performance when project budget balances are not of interest. (#2575)
The function will now complain if "From" period is later than the "To" period.
Empty revisions are now shown as empty instead of "0". (#2671)
Supported asterisk (*) for the balance types argument. (#2700)
EXPANDPROJECTHISTORY mistakenly ignored the revision parameter when IncludeInactive was set to TRUE. (#2632)
The screen would flicker multiple times in some workbooks containing the VXTEXTSPLIT function. (#2634).
During Copy without formulas, Velixo could not copy some workbooks that had auto-filter values that were not readable through the Excel Interop model. In the current version, Velixo will preserve auto-filters on the best-effort basis only. (#2644)
Creating a distribution list on a system with French regional settings could incorrectly set up the distribution format drop-down. (#2703)
Velixo now uses FIPS-compliant hashing algorithms, allowing usage on systems with strict FIPS policy enabled. (#2610, #2626)
On older non-365 versions of Microsoft Excel, Velixo's experimental mechanism for displaying spilling ranges did not work with R1C1-style references, or on systems using the ";" list separator (#2617).
GL transaction writeback was not possible when default non-project code in the ERP system was renamed from "X" to anything else. (#2618)
Project functions could return zero balances in case Velixo inquiries were configured on legacy Acumatica versions (2018R2 and older) and never upgraded or recreated (#2611)
On older systems without WebView 2 browser engine, got rid of an unexpected error pop-up during start-up. (#2614, #2615)
This version adds support for ERP version 2022R2 and drops official support for 2020R1.
Breaking: due to Microsoft rolling out its own TEXTSPLIT function that is incompatible with Velixo's TEXTSPLIT, we were forced to rename our function to VXTEXTSPLIT. If you used Velixo's TEXTSPLIT function previously, your reports need to be updated to the new function name.
New EXPANDPROJECTHISTORY() function - like ACCOUNTSWITHHISTORY(), but for project module.
Drill-down sheets will now contain the Turnover column in addition to separate Debits and Credits. (#2498).
Custom columns in GL writeback now support Excel date values. (#2494)
In Copy without formulas and Report Distribution, any spill range references like A9# will continue to work! (#2500)
Improved the general refresh performance by up to 10% (#2560), and improved performance of project reports in Velixo by up to several times on large reports! ?. (#2549, #2569)
WRITEBACK() function arguments can now be used in a dynamic-aware manner. For example, you can now specify multiple Excel range references like A1# as separate arguments, and it will work seamlessly with the writeback function. (#2595)
Wildcard range patterns like ABC?? in Velixo functions are now case-insensitive. (#2588)
The "refresh pivot tables" distribution template setting now also works with the PDF report distribution format. (#2508)
Excel could crash during Copy Without Formulas or Report Distribution when Velixo could not break links to the source workbook. (#2602)
It was impossible to distribute locked worksheets in Report Distribution when those sheets contained auto-hiding zero rows or columns. (#2600)
For large reports consuming a lot of GI() data, Velixo could keep re-requesting the data without ever finishing the refresh. (#2593)
This update is recommended.
A drill-down COM error occurred when a drilled cell is part of a spilled range of a function that refers to a different worksheet.
Drill-down arrows would not be removed sometimes.
Velixo self-diagnostics generated a lot of network traffic on large reports.
This update is recommended.
Due to a bug in Acumatica 2022R1, a Velixo GL generic inquiry could be created incorrectly for a small subset of clients, leading to erroneous zero balances for some GL accounts. This update adds extended validation for the inquiry during the connection process. If any issues are found, Velixo will propose to automatically upgrade the inquiry.
Velixo range expressions (e.g. for ledgers and branches) were unnecessarily case-sensitive
Report Distribution and Copy Without Formulas: when the resulting copy of the workbook contains pivot tables still referencing the original workbook, Velixo will smartly try to rewire their data range to the copied workbook!
Additional performance improvements for Auto-Hide Zero Rows!
Ensured that Hide Zero Rows also hides rows containing mixed zeroes and blanks.
Fixed a potential COM exception that could occur during Copy Workbook Without Formulas or Report Distribution in case the report contained pivot tables.
Fixed the button caption for forgetting auto-hide ranges.
Auto-Hide Zero rows sometimes triggered prematurely during recalculation, which led to some zero rows remaining visible.
Distribute All button could sometimes remain disabled after report distribution.
Greatly improved the performance of the Auto-Hide Zero Rows/Columns functionality.
Improved the error message when a user tries to distribute hidden sheets in PDF/Excel formats
Velixo ribbon will not allow the user to create writeback worksheets when there is no active workbook.
"Type mismatch" error could sometimes surface during VBA macro execution due to Velixo's background processing logic.
If a report distribution into a OneDrive folder fails due to OneDrive holding access to the folder, Velixo will display a more descriptive error message.
When processing selected tabs during report distribution, Velixo will ignore the case in tab names.
Import scenarios in the Generic Writeback worksheet creation dialog are now sorted by name.
Improved the error message upon encountering a non-existent import scenario name in New Generic Writeback Worksheet.
Pivot tables in distributed reports were still looking at the original file for source data.
Unexpected error messages could be displayed after a user attempted to close an unsaved file and then clicked "Save" in the pop-up prompt.
A null reference error could very rarely occur during refresh.
Excel could sometimes freeze during the auto-connection process when connection credentials were not remembered in the file.
Some import scenarios could be missing from the Generic Writeback worksheet creation dialogue.
Fixed an error pop-up when the same file was opened in the two-window mode.
Minor fixes and improvements.
Added the option to attach files to records uploaded during Generic writeback.
Generic writeback now supports single sign-on connections (requires ERP version 2022R1 or newer).
Project functions are now dynamic-aware: their output will resize together with their input.
A welcome carousel pop-up is now displayed on start-up.
Better UX and status reporting during writeback.
Improved performance for import scenario list retrieval in generic writeback worksheet pop-up. You may need to click Validate inquiries in the connection manager and configure the VelixoReportsPro-ImportScenarios inquiry.
Generic writeback worksheet pop-up and function Intellisense hints now also display ERP screen IDs and titles in addition to the import scenario name.
Improved drill-down performance on large worksheets
Improved "single-click" writeback experience involving multiple writeback scenarios and subsequent writebacks reusing the result of previous write-backs.
Velixo now supports displaying total record count in the status bar during refresh on ERP version 2022R1 and newer.
WRITEBACKPROJECTUPDATEBUDGET will not be executed during write-back in case the preceding project budget writeback fails.
The "contains"-style smart expand in GIFILTER (*containedtext*) will now work without the user having to check "Always load the entire Generic Inquiry..." option.
GIFILTER now supports null literals as criteria.
GIFILTER will now return an error when a comparison operator has a criteria without an explicit operand ("=", "<", ">")
The "Validate inquiries" command will now display a success message in case no issues are found.
The "Recreate inquiries" command in the Connection Manager could create extra inquiries that were redundant given the licensed modules.
Hide Zero Rows / Columns always worked on the whole spill range of a cell even if the user selected only a part of it.
Excel workbooks embedded as COM objects in Word documents crashed when Velixo was installed on the system.
Invalid OData filters in GI function sometimes resulted in a diagnostic window being displayed instead of displaying as an in-cell error message.
The "Import selected cells or worksheets" command did not work when multiple worksheets were selected.
On older systems, clicking the Help button on the ribbon could result in an error.
New generic writeback sheet pop-up dialog could display an empty connection drop-down after saving the workbook under a new name.
Exception thrown upon Generic Writeback sheet creation when logged in under SSO.
COM exception could happen upon closing a distributed report
If "New workbook" was selected as a drill-down worksheet destination, and the name of the source tab was too long, the drill-down worksheet could not be created.
GI options were not created for GI function calls in case another workbook with the same connection, using the same GI, was opened in parallel.
Scheduled distribution invoked from the command line did not properly respect the "hidden" and "silent" command line flags.
Values returned as out-parameters from Generic Writeback could not always be used in subsequent writebacks because they contained trailing spaces.
Due to a bug in some ERP versions, using GIFILTER's "smart expand" feature or contains() / startswith() / endswith() functions in a GI filter, resulted in an error.
❗ Action may be required
WRITEBACKARGUMENTS() will now return a row vector instead of a column vector because a row vector is expected by the WRITEBACK function. You may need to remove any TRANSPOSE() calls around this function in case you have already tested Generic Writeback under Velixo Insider program.
The DataColumnNames argument in generic WRITEBACK() function is now a required argument.
WRITEBACKREFRESHDATA() now does not have any argument.
Was this article helpful?
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
We appreciate your effort and will try to fix the article