We released an update to Stonefield Query for Sage Pro ERP version 3.3 today. It has the following new features:
- Sage Pro 2010 is now supported.
- Relationships were created between the PO Transaction File and the Inventory Transaction, Item at Location, and Purchase Order Master Files.
- There's a new Quantity Open field (which is Qty Ordered - Qty Received) in the Order Entry Transactions File.
- There are new On Order PO and Allocated SO fields in the Inventory Master File.
- You can configure Stonefield Query to use the Sage Pro DSN directly instead of going through the Sage Pro COM component when accessing SQL Server. To do this, add the following to DATA.INI:
- In the Field Properties dialog, the Summary option has a new choice: Count Distinct. The difference between Count and Count Distinct is that Count counts the number of records while Count Distinct counts the number of records having unique values on this field. For example, if there are 100 order records but all orders were placed this week, using Count on the Order Date field would display 100 but Count Distinct would display 7 (assuming at least one order was placed every day this week). Also, the Summary option is now available for all field types, not just numeric fields.
- The Display date as option in the Field Properties dialog has a new choice: Hour, which displays the hour portion of the datetime value.
- If you use a date or datetime field in the X-axis, missing values are automatically added to the chart, and the range of those values respects any date filter you use. For example, in the following chart, the only dates that had orders were 07/04, 07/05, and 07/08, but the filter condition was Order Date is between 07/01/1996 and 07/08/1996, so all days between those dates appear whether they had any orders or not:
- The Chart Type page in Step 4 of the Chart Wizard has a new Summary report option, which is turned on by default. Turn this option off if, instead of displaying summarized values, you want individual values charted.
- The Formula Editor has a new Send formula to database engine option that allows you to specify whether the database engine evaluates the formula or whether Stonefield Query requests any fields used in the formula from the database engine and then evaluates the formula itself.
- If you use an existing formula in a new formula, the existing formula is no longer expanded to show its definition in the new formula; instead, just its name appears, as it did when you created the new formula. For example, suppose a formula called Total Price is Unit Price * Quantity. If you create another formula called Commission, which is Total Price * 0.05, the formula displays as Total Price * 0.05 rather than Unit Price * Quantity * 0.05 as it used to in previous versions.
- Cross-tab reports have a new "Show percentage of total" option.
- Blank column headings now appear as "(None)" in cross-tab reports.
- In a multiple database report, if the query for one database fails for a reason other than a connection problem, the report continues to run if the Continue multi-database report if cannot connect to one database setting in the Options dialog is turned on.