Sage 100

 View Only
  • 1.  CI_Report_Unable:view Picking Sheet Printing Repo

    Posted 11-01-2014 13:01
    CI_Report_Unable:view Picking Sheet Printing Report. The string is non-numeric"" on a very complex pick sheet that I didn't design. If we change one formula from this: tonumber({CI_Item.ShipWeight})*{SO_PickingSheetWrk.QuantityOrdered} to this: tonumber({CI_Item.ShipWeight})*{@05 New Case Qty}) the error comes up. I've tried to reverse engineer through all of the formulas and can't find anything causing the error. If I leave the {@05 New Case Qty} formula on the lines of the pick sheet it doesn't cause the error, only when i change it in the other formula. Is there a way to debug a crystal message like this and figure out what specifically is causing the issue. Sage's resolution is to create a new form code which helps a lot.


  • 2.  RE: CI_Report_Unable:view Picking Sheet Printing Repo

    Posted 11-01-2014 13:13
    Not sure if its a typo on this email, but you have an extra "")"" after the {@05 New Case Qty}. What is the result of the @05 formula when you put it on the lines by itself?. Is it numeric? it sounds like it might be resulting in text rather than a number


  • 3.  RE: CI_Report_Unable:view Picking Sheet Printing Repo

    Posted 11-01-2014 13:28
    What happens if you only use tonumber({@05 new case qty})? If you still get the error then it may be a data typ eissue in one of the fields in @05 new case qty. Look at the data ... could be a space or other string that is not convertible to numeric.


  • 4.  RE: CI_Report_Unable:view Picking Sheet Printing Repo

    Posted 11-01-2014 13:30
    It may be that the formula is trying to multiply the non-numeric values before it applies the tonumber function.... tonumber each individually then multiply them.


  • 5.  RE: CI_Report_Unable:view Picking Sheet Printing Repo

    Posted 11-01-2014 13:39
    thanks for the feedback and ideas, I'll play around with that 05 new case qty formula a bit more, it does work fine on it's own on the lines


  • 6.  RE: CI_Report_Unable:view Picking Sheet Printing Repo

    Posted 11-01-2014 13:47
    I would cretae a new test formula and just put {@05 new case qty}+1 in there. see if that does results in an error


  • 7.  RE: CI_Report_Unable:view Picking Sheet Printing Repo

    Posted 11-01-2014 13:49
    I'd stick another ToNumber() in front of the @05...


  • 8.  RE: CI_Report_Unable:view Picking Sheet Printing Repo

    Posted 11-01-2014 14:09
    I put the end of the if/then/else formula into it's own formula and it works fine: tonumber({CI_Item.ShipWeight})*{SO_PickingSheetWrk.QuantityOrdered} So it's tied to another piece of the if/then/else state statement - I think it's the if isnull({CI_Item.ShipWeight}) then 0 - which doesn't cause a problem when the else result is: tonumber({CI_Item.ShipWeight})*{SO_PickingSheetWrk.QuantityOrdered} so strange, it just doesn't make sense. Anyway, is there a simple formula to say if the result of tonumber({CI_Item.ShipWeight}) is not a number or causes an error then 0? If I can throw that in there in case there are any bad/non-numeric ship weights I think I'll be good.


  • 9.  RE: CI_Report_Unable:view Picking Sheet Printing Repo

    Posted 11-01-2014 14:23
    ok - scratch that - I have the exact same calc as two different formula fields in the lines - but one of them is being summed up to GroupFooter 1. So it's when it tries to sum that up - the formula is just: Sum ({@WSLineCaseWt}) - the report bombs. I just tested adding a summary on the new formula fied I added and that forces the report to bomb as well. Any other ideas as to why summing a number field up to group footer 1 would cause non-numeric string error?


  • 10.  RE: CI_Report_Unable:view Picking Sheet Printing Repo

    Posted 11-01-2014 14:34
    I would print out the value of each variable to determine which variable is non numeric. Also i believe the syntax to check for a null value is: if isnull({CI_Item.ShipWeight}) = TRUE then 0 else {CI_Item.ShipWeight};