Need more, need help now?
- - - - - - - - - - - - - - - - - - pay-as-you-go support - no contract - tenth of an hour billing - expert help - fast service - no call queues
Need integration?
- - - - - - - - - - - - - - - - - - with your shipping system - website - invoicing system - crm - cms - manufacturing - order import - back to back orders..
Need a report?
- - - - - - - - - - - - - - - - - - Excel reporting that pulls data from Sage - custom layouts - layouts that change adapt to your brands and/or for drop shipping.
Want web hosting?
- - - - - - - - - - - - - - - - - - Your own domain name - email - a shop - wordpress - woo commerce - ticket systems - help desks - forums - portals

Expressions in Report Designer

Sage 50 general help forum - Free help and support for all general issues
Post Reply
Loz
User
User
Posts: 2
Joined: 10 Sep 2008, 11:21

Expressions in Report Designer

Post by Loz » 10 Sep 2008, 11:34

I am using v14 Sage Line 50 Professional. I am new to SAGE and am self taught.

I am trying to add a new calculated field to a PNL report to show the number of units sold as well as the balance. I added the expression (based on the CATEGORY.DISP_MTH1 field),
'PeriodAggregate("STOCK.QTY_SOLD_MTH", CRITERIA.TRAN_PERIOD_FROM, CRITERIA.TRAN_PERIOD_TO)'

but I get an error message saying STOCK.QTY_SOLD_MTH1 does not exist. However, when I just add STOCK.QTY1_SOLD_MTH1 as a field, it does show the value stored in that field (so does exist!). I get around it by having the expression
'STOCK.QTY_SOLD_MTH1+STOCK.QTY_SOLD_MTH2+STOCK.QTY_SOLD_MTH3+STOCK.QTY_SOLD_MTH4+STOCK.QTY_SOLD_MTH5+STOCK.QTY_SOLD_MTH6+STOCK.QTY_SOLD_MTH7+STOCK.QTY_SOLD_MTH8+STOCK.QTY_SOLD_MTH9+STOCK.QTY_SOLD_MTH10+STOCK.QTY_SOLD_MTH11+STOCK.QTY_SOLD_MTH12'
and this does give the total, but of course would not take notice of the period from/to criteria.

I added the STOCK table in the Data joins as a Left Join with NOMINAL_LEDGER

Can anyone shed any light on why the PerdiodAggregate function does not appear to work in this instance ? Have I missed a parameter somewhere ?

Thankyou

Loz
User
User
Posts: 2
Joined: 10 Sep 2008, 11:21

Sorted !

Post by Loz » 10 Sep 2008, 13:32

I think I have finally got this working !

I added a new expression field called UNITS by using the toolbox AND the former field I created called STOCK.QTY_SOLD_MTH1 was still there (see above), but when I deleted this former field, it errored again, so having this variable as a field on the report as well as the expression seems to be the missing link. I then hid it (visible=false).

All seems to be working fine now

Post Reply

Who is online

Users browsing this forum: Amazon [Bot] and 21 guests