Stonefield Query Version 3.2 Build 3226

We posted updated versions of the Stonefield Query SDK, Stonefield Query for Sage Accpac ERP, and Stonefield Query for Sage Pro ERP today with the following changes.

All Versions

• Stonefield Query is now available in Spanish thanks to Juan Antonio Santana.
• Stonefield Query now supports linked reports that pass a value to a report with an "is between" ask-at-runtime condition by using the same value for both the starting and ending values.
• Multiple text lines (for example, in a memo field) are put into the same cell in a Microsoft Excel spreadsheet rather than separate cells.
• An issue where the dollar sign is cut off for currency values or the value shows as **** when the largest-width item in the column is a negative value was fixed.
• The correct currency symbol now displays in charts.
• You can now call the built-in GetConditionValue function from an expression in the Advanced Report Designer.
• Using a currency field in the data area of a cross-tabulation report but formatting it as "Count" no longer displays the currency symbol.
• Cross-tab data columns are now sized properly in the unusual case where all row totals are zero (that is, individual columns have a mixture of positive and negative values so that the row total is zero and all rows have this condition).
• You no longer get an error if you edit a group in the Maintain Users and Groups dialog, select the Users tab and when asked to save, choose No, and then change the license type.

SDK

• Joins involving fields with the same name as the tables they are in (such as "Category.Category") are now handled properly.
• You can now access the FilterConditions object in DataEngine.FinalizeSQLStatement scripts.
• Anonymized projects no longer give an error looking for SQOUTPUT.EXE when you print a report.
• Running a report with ask-at-runtime filter conditions and a custom SQL statement from SQProxy no longer displays the ask-at-runtime dialog if you specify that the conditions should be ignored by passing blanks for their values.

Sage Accpac ERP

• New Combined Invoices & Credit Notes and Combined Invoice & Credit Note Details tables in Order Entry make it easy to report on both invoices and credit notes on the same report.
• You can call new built-in GetStartingBalance and GetStartingBalanceFYPeriod functions in an advanced layout report to display the starting balance for the specified account in the specified fiscal year and period.
• There's a new Quantity on Hand (Current) field in Inventory Control Location Details table. By default, Sage Accpac does not store the quantity on hand but calculates it. When day end is run, all pending transactions are applied and the Quantity on Hand (Last Day End) field is updated to the true quantity on hand. The Quantity on Hand (Current) field allows you to see what is on hand without running day end. It is calculated as Quantity on Hand (Last Day End) + Quantity Received Not Costed - Quantity Shipped Not Costed + Quantity Adjusted Not Costed.
• The built-in functions for date expressions, such as "Today's Date", now work properly for Sage Accpac dates.
• For optional fields that have descriptive as well as code values, a new "Optional field Description" field is available to display the descriptive value.
• There are several new fields in the General Ledger Posted Transactions table which you can use to create more compact transaction listings: Batch-Entry, which combines the batch and entry numbers, Source, which combines the Source Ledger and Source Type values, and Fiscal Year-Period, which combines the Fiscal Year and Period.
• Stonefield Query no longer permits a relationship between Accounts Receivable Customers and Project and Job Costing Projects unless you are using Sage Accpac 5.5 or later.
• The Purchase Order and Account Sets tables are now included in the Order Entry module.
• Since the Salesperson table was removed from Order Entry in Sage Accpac 5.5, all relationships to it now work with the Accounts Receivable Salesperson table.
• The Account Segment Code fields in the General Ledger Accounts table now display the segment code rather than its descriptive name. However, new Account Segment Description fields were added to display the descriptive names. This gives you the best of both worlds: you can display either the code or descriptive name or both.

Sage Pro ERP

• Stonefield Query now displays the proper values for the Transaction Type field in the Inventory Transaction table for issues and receipts.
• All fields in "current + history" tables now have same data type and size as those in the current tables.
• Stonefield Query now properly handles fields that were renamed in Sage Pro version 7.0 so you can use Stonefield Query with Sage Pro version 6.5 and earlier.
• The MACODE field in the Order Entry Transaction table is no longer available since it's obsolete.