Sage 100

 View Only
  • 1.  Sage Intelligence - keep getting error re ""Year, M

    Posted 07-15-2016 08:57
    Sage Intelligence - keep getting error re ""Year, Month, and Day parameters describe an un-representable DateTime"" when running any reports that use the GL_DetailPosting file - such as the actual Detail report, or any Designer Add-In report. I've run Crystal on the date fields, used VI, and visually scanned and see nothing wrong with any dates. The fact that it says ""parameters"" leads me to believe it's NOT the date field that is the issue, but I can't figure out what else it could be. I can run the financials that are not Designer Add-in reports just fine, but they use Period-Posting History file. Help (whimper)... Oh, damn it, it never fails - I just have to write it all down and I figure it out. There was a period ending date missing in one of the fiscal periods in Fiscal Year Maintenance.


  • 2.  RE: Sage Intelligence - keep getting error re ""Year, M

    Posted 07-15-2016 09:21
    Check the Select statement in your Connector module. There is something weird about how it's selecting dates and for what it's worth, I do suspect that it's something bizarre about the underlying data structure in Sage. For example, in mine, I have a Container called GL Transactions 1-0. I get a error message, however, if I go to the Source Container (Join) field, and delete references to the date, the report in RM will run, at least. For example, I change this: GL_DetailPosting,GL_Account WHERE GL_DetailPosting.PostingDate >='@StartDate@' AND GL_DetailPosting.PostingDate <='@EndDate@' AND GL_DetailPosting.AccountKey = GL_Account.AccountKey to this: GL_DetailPosting,GL_Account WHERE GL_DetailPosting.AccountKey = GL_Account.AccountKey And the report runs without trouble. Yours may be different, of course, but you get the idea, at least. Usual cautions apply, ergo, copy the original statement to Notepad and save it before editing it so you can go back if it's merited somehow. Lou