Prev
Next
Forums Performance Management Smart Notification

Smart Notes Infoset Update error

 8 Replies
 0 Subscribed to this topic
 14 Subscribed to this forum
Sort:
Author
Messages
mark.cook
Veteran Member
Posts: 444
Veteran Member
6/26/2009 1:49 PM
    We upgraded last night our LBI server to 9.032. Once completed, I was running through validation and my infosets will not update. I am getting an invalid query message.

    When I take my selection criteria out to limit the records in the query I can see the results in preview.

    Does anyone know of syntax changes that would cause this to happen between versions?
    Matthew Nye
    Veteran Member
    Posts: 514
    Veteran Member
    6/26/2009 2:21 PM
      Can you post youre query? Also, have you looked at your WebSphere log files for any stack traces?
      If any of my answers were helpful an endorsement on LinkedIn would be much appriciated! www.linkedin.com/pub/matthew-nye/1a/886/760/
      mark.cook
      Veteran Member
      Posts: 444
      Veteran Member
      6/26/2009 3:31 PM
        FILE=EMDEPEND&FIELD=COMPANY;COMPANY.NAME;CUR-AGE;EMPLOYEE;EMPLOYEE.FULL-NAME;EMPLOYEE.EMP-STATUS;BENEFITS.START-DATE;SEQ-NBR;DEP-TYPE;FULL-NAME;BIRTHDATE;DISABLED;STUDENT;HL-COV-FLAG;DN-COV-FLAG;DL-COV-FLAG;&SELECT=BIRTHDATE<=19900625%26HL-COV-FLAG!=N%26DN-COV-FLAG!=N%26DL-COV-FLAG!=N%26STUDENT=Y%26DISABLED=N%26DEP-TYPE!=S%26BENEFITS.START-DATE%3E%3D01%2f01%2f2008&NOHEADER&OUT=CSV
        Matthew Nye
        Veteran Member
        Posts: 514
        Veteran Member
        6/26/2009 4:14 PM
          i wonder if the decoded special characters got corrupted in the upgrade. try rebuilding the query in what ever tool you used.
          If any of my answers were helpful an endorsement on LinkedIn would be much appriciated! www.linkedin.com/pub/matthew-nye/1a/886/760/
          mark.cook
          Veteran Member
          Posts: 444
          Veteran Member
          6/30/2009 1:27 PM
            Well I have been working a case with Lawson on this since Friday. What I have found so far is that I needed a new datasource set up with the New Smart Notes where the URL appears like the following:
            http://app server/servlet/Router/Data/Erp

            I also had to go to where smartnotes puts in the NOHEADER and edit that to say NOHEADER=NO

            I am still having syntax errors when I use the following to find records:

            SELECT=BIRTHDATE<=[date=-MS228 fmt=yyyyMMdd]

            I will update this when I find the answer to others can use the format as well. If anyone has suggestions while I wait on Lawson let me know
            Ruma Malhotra
            Veteran Member
            Posts: 412
            Veteran Member
            6/30/2009 1:53 PM
              Can you try the fol. syntax:

              select BIRTHDATE=to_date('[date=-DS0 fmt=yyyy-MM-dd]','yyyy-mm-dd')

              Where -DS0 means today. if you want 14 days back you can also use -DS14. Depending on the number of days in your time you can format the date range.
              mark.cook
              Veteran Member
              Posts: 444
              Veteran Member
              6/30/2009 4:35 PM
                Thanks for the help but no luck with that format either.
                mark.cook
                Veteran Member
                Posts: 444
                Veteran Member
                7/1/2009 11:18 AM
                  Lawson came back with another suggestion and it worked. I have to escape out the special charactors in the select statement.

                  My original looked like:

                  SELECT=BIRTHDATE<=[date=-MS228 fmt=yyyyMMdd]

                  The New version looks like:

                  SELECT=BIRTHDATE%3C%3D[date=-MS228 fmt=yyyyMMdd]

                  The new query wizard will put these in on new queries but blow up in you try to copy the old format in. I haven't seen this documented anywhere, so hopefully this helps someone out.
                  mark.cook
                  Veteran Member
                  Posts: 444
                  Veteran Member
                  7/8/2009 12:27 PM
                    A PT is being developed for this so if anyone runs into this look for PT 183379 to correct