Add Ins Error

 9 Replies
 1 Subscribed to this topic
 78 Subscribed to this forum
Sort:
Author
Messages


stephanie











Veteran Member



Posts: 330




Veteran Member



    Can someone tell me what this addins error may mean -

    Filter cannot begin with '&' or '|'

    We just moved to apps v901, and queries that have never had problems are now returning this error.  Seems to happen most often if I try to use criteria that is any option other than "=".  I'm on the most recent add-ins version

    Thanks in advance - I'm almost bald from pulling my hair out over this one!!



    Greg Moeller











    Veteran Member



    Posts: 1498




    Veteran Member



      Stephanie: Are you using queries built with your previous app version (900) and trying to make them work with your new 901 apps? What happens if you try and start over and build one from scratch?


      stephanie











      Veteran Member



      Posts: 330




      Veteran Member



        Hi Greg - I've rebuilt every darn one - no cheating!!


        Greg Moeller











        Veteran Member



        Posts: 1498




        Veteran Member



          I know that we had to rebuild several of ours when we upgraded.


          Greg Moeller











          Veteran Member



          Posts: 1498




          Veteran Member



            I know that I've seen that error before, let me check my doco.


            Greg Moeller











            Veteran Member



            Posts: 1498




            Veteran Member



              Sorry, Stephanie, I've looked everywhere and cannot locate a resolution for this.


              Gary Padgett











              Veteran Member



              Posts: 90




              Veteran Member



                Stephanie, do you see anything in IOS.log and/or webserver log files? I am curious as to what the whole string is. Or is there more stuff in the add-ins error log on the PC?


                stephanie











                Veteran Member



                Posts: 330




                Veteran Member



                  Here is an example of the addins error log one time when I received the error -

                  "ACTUAL CALL STRING THAT GENERATED THE ERROR:"
                  "https://paywebserv.house.gov/servlet/Router/Data/Erp?PROD=STAFFPROD&FILE=PRTAXLOC&INDEX=PXLSET1&KEY=4832&COND=ACTIVE&FIELD=EMPLOYEE;EMPLOYEE%2EFULL%2DNAME;EMPLOYEE%2EEMP%2DSTATUS;DED%2DCODE;ACTIVE%2DFLAG;EMP%2DDEDUCTION%2ERES%2DCODE;EMP%2DDEDUCTION%2EEFFECT%2DDATE;EMP%2DDEDUCTION%2EEND%2DDATE&SELECT=%26DED%2DCODE%3DTSMD&OUT=CSV&DELIM=%09&NOHEADER=TRUE&OTMMAX=2&OTMDELIM=~&NEXT=TRUE&MAX=1000"
                  "ERROR KEY = FILTER_STARTS_WITH"
                  "ERROR MESSAGE = Syntax error in filter: &DED-CODE=TSMD. Filter cannot begin with '&' or '|'.

                  There are additional "error details" - a LOT of lines of this -

                  " com.lawson.ios.dig.db.DmeException: FILTER_STARTS_WITH
                  at com.lawson.ios.dig.db.FilterManager.parseRawFilter(FilterManager.java:298)
                  at com.lawson.ios.dig.db.FilterManager.(FilterManager.java:200)
                  at com.lawson.ios.dig.db.DigObject.initFilterComponents(DigObject.java:799)
                  at com.lawson.ios.dig.db.DigObject.executeInternalRequest(DigObject.java:299)
                  at com.lawson.ios.dig.db.DigObject.executeRequest(DigObject.java:183)
                  at com.lawson.ios.dig.db.Dme.executeRequest(Dme.java:76)
                  at com.lawson.ios.dig.ErpDmeAgent.processRequest(ErpDmeAgent.java:114)

                  Do you need more? Many thanks for the efforts to assist me!!


                  Gary Padgett











                  Veteran Member



                  Posts: 90




                  Veteran Member



                    I think the error is coming from the part where it says
                    &SELECT=%26DED%2DCODE%3DTSMD
                    I believe the %26 is what is generating the error. The field name is just DED_CODE.
                    Can you try this string in your browser, removing that %26?


                    Sherry Shimek











                    Advanced Member



                    Posts: 43




                    Advanced Member



                      When we upgraded, we installed the most recent version of MS Addins and then rebuilt all of our queries to resolve this issue. It may not be necessary for every current query, but it was faster to rebuild them once with an upgraded MS Addins version and the upgraded tables instead of painfully trying to run each query.
                      Sherry Shimek Catholic Health Initiatives Englewood CO