3 Replies Latest reply on Jan 22, 2019 2:47 PM by Cris Coffey

    Track-IT 2018.3! Multi-Value Parameter Report Error

    Edith Murillo

      Has anyone used the multi-value option as a report parameter?  I keep getting a runtime error when I try to edit the report when I use the Design Report button.  I'm also getting an error when I try to run the report of "trying to populate the datasource and the exception is no mapping exists".    I'm wondering if this is a known issue in this version or there's some config we need to look into.     

       

        • 1. Re: Track-IT 2018.3! Multi-Value Parameter Report Error
          Cris Coffey

          Try 2 things. First, in the datasource settings on the report, if the name of the data source is just “Data Source”, click the Add Data Source button, select “Track-It! Data Source”, then save the report, close it, and re-open it.  After that try the parameter again. Then in the filter, be sure to put any date filter logic after all other filter logic and see if that helps. If those 2 things do not help, you will probably need to contact support to get some help troubleshooting.

          • 2. Re: Track-IT 2018.3! Multi-Value Parameter Report Error
            Edith Murillo

            Thanks Cris for your response!

            Since I couldn't go back to make those changes, I create a simple new report using the wizard. I added the title, selected 3 fields, created a string parameter, selected the multi-value option and added the filter string logic under actions as  [ticket id] in (?stringparameter). I selected the Preview and successfully ran the report using 2 values for ticket #s.  I saved the report, closed it, however, when I went back to edit the report it gave me the runtime error. The funny thing is that I can run the report with no issues. Very weird!  I already opened a call with Support. I was just hoping someone else had encountered this. Thanks again

            • 3. Re: Track-IT 2018.3! Multi-Value Parameter Report Error
              Cris Coffey

              That is very weird. Hopefully support can figure it out and it’s something simple.