4 Replies Latest reply on Feb 5, 2019 10:36 AM by vinitha.velayutham

    Issues in initial loading of drill down report

    vinitha.velayutham

      I’m looking at a strange issue in Tableau drill-down reports and see if you can help me out.  I'm using Tableau 10.2 version, and the data is Live (not an Extract) from the SQL DB server.

       

      1. This is the main dashboard:  https://qa-tableau.abc.com/#/views/Det/DetMetrics ,which has URL action defined as: https://qa-tableau.abc.com/#/views/Detail/<ReportName>?DKey=<DKey>&MKey=<MKey>  for the drill-down report.

      From the deployed Tableau report,  I choose a value and try to drill to the detailed report from the browser (Chrome).

      2. An error pop up as below. Also, the URL doesn’t show the field iid, which is supposed to be auto generated by Tableau server.  https://qa-tableau.abc.com/#/views/Detail/DetailQ>?DKey=40&MKey=12

      (on opening the console, this error was shown as: Failed to load resource: the server B3997C6238EB4FDDB5E84132013A729E-0:1:1 responded with a status of 500: Internal Server Error)

      Error.png

      3. I open the detailed report separately and it opens just fine also with a random value for iid https://qa-tableau.abc.com/#/views/Detail/DetailQ&iid=3

      4. I then go back to the main dashboard again and choose a value to drill-down, leaving the blank report open in the previous tab.

      5. Now the detailed report with data opens fine with iid auto generated on the URL. https://qa-tableau.abc.com/#/views/Detail/DetailQ>?DKey=40&MKey=12&iid=2

      I cleared my browser cache and tried to check this again. The same steps 1-5 above were repeated. However,

      • After I open the detail report individually, and leave the tab open, if I choose to drill down from the main dashboard – no issues in drill down.
      • After I open the detail report separately but close the tab and choose to drill down from the main dashboard – the drill down report doesn’t load at all.

       

      I suspected this has to do with Tableau cache and tried the below steps discussed in other forums but nothing fruitful.

      1. I included “&refresh” option in URL actions, assuming this is due to cache but the data takes 12+mins to load, which is not acceptable as per our standards. Like this: https://qa-tableau.abc.com/#/views/Detail/<ReportName>?DKey=<DKey>&MKey=<MKey>&refresh
      2. I removed # from the URL and tried too, but the same error occurred. Like this: https://qa-tableau.abc.com/views/Detail/<ReportName>?DKey=<DKey>&MKey=<MKey>
      3. I also tried including a value for iid at the end of my URL (even though it wasn't advised to do so), but that too worked for once in my machine, but the user got the same error. Like this: https://qa-tableau.abc.com/#/views/Detail/<ReportName>?DKey=<DKey>&MKey=<MKey>&iid=1

       

      While the page loads initially for the first time after deployment,  I keep encountering this issue. The users have happily signed off UAT, considering the quality of data is correct. But I would like to know if this is a known issue or there can be anything changed to fix the code, before I move to Production.

       

      Regards,

      Vinitha!

        • 1. Re: Issues in initial loading of drill down report
          Naveen B

          Hi Vinitha.

           

          Error showing as Incorrect data type did you check that column which you are passing the action

          along with this

          Which database you are using ?

           

          Regards,

          NB

          • 2. Re: Issues in initial loading of drill down report
            Dan Huff

            Vinitha--

             

            I can't explain immediately why your action would work with the blank tab and not initially. I think this may be something you could bring up with Tableau Support by opening a case here: Support Case | Tableau Software

             

            In creating your case, it would be incredibly helpful if you could do the following in addition to anything else that may be requested on the case page:

             

            1. Try this workflow using an extract
              • I'm wondering if there is something inconsistent with how the data types are being handled against the live connection
            2. If you can reproduce this issue with the extract, it would be great if you could include a workbook in the support case
            3. Reproduce the issue a couple times and then take a ziplogs to capture what happened
            4. Write down the error as you did above so the team has an easy starting point (they will likely search for the session captured in the error message)
            5. Provide this ziplogs as part of your case

             

            Hopefully we can get you some help on this. Thanks for reaching out here.


            Dan

            • 3. Re: Issues in initial loading of drill down report
              vinitha.velayutham

              Hi Naveen,

               

              I’m using SQL server 2016 as the backend for Tableau.

               

              ReportName is a calculated field (datatype is String) which is passed through the URL action, and the formula used is as below.

               

              Role:

              Discrete Dimension

              Type:

              Calculated Field

              Contains NULL:

              No

              Locale:

              Root

              Sort flags:

              Case-sensitive

              Column width:

              24

              Status:

              Valid

              Formula

              IF [MKey] = 11
              OR [MKey] = 13 THEN
              "DetailB"
              ELSE
              "DetailQ"
              END

              DKey and MKey are the other 2 fields(datatype is Integer) taken from underlying table and passed through URL action.

              DKey

              Role:

              Discrete Dimension

              Type:

              Database column

              Remote column:

              [v_081_abc].[DKey]

              Remote type:

              Four-byte, signed integer

              Contains NULL:

              No

              Status:

              Valid

              MKey

              Role:

              Discrete Dimension

              Type:

              Database column

              Remote column:

              [v_081_abc].[MKey]

              Remote type:

              Four-byte, signed integer

              Contains NULL:

              No

              Status:

              Valid

               

              Regards,

              Vinitha.

              • 4. Re: Issues in initial loading of drill down report
                vinitha.velayutham

                Hi Dan, Naveen,

                 

                I might have found a finally acceptable explanation to the issue I had.

                I found an article closely related to my issue: https://kb.tableau.com/articles/Issue/errors-tableauexception-or-could-not-find-sheet-with-name-sheet-0-when-publishing-a-workbook-to-tableau-server-or-and-tableau-online

                This is an issue noted in lower versions of Tableau 10.2, 10.3, etc. The suggested fix is to upgrade Tableau version and modify the code again.  Our initial code was developed in Tableau 10.0 in 2016, and there have been no changes since 2016 to the code. Tableau QA and Production servers must have been running at the same 10.0 version at that time.

                However coming to 2018/2019, Tableau QA and Production servers are now in 10.2. So due to compatibility issues, I cannot publish 10.0 code to 10.2 server.

                https://onlinehelp.tableau.com/current/desktopdeploy/en-us/desktop_deploy_compatibility.htm

                So I modified the code developed in 10.0 on 10.2 version and published to the server, and started getting the exception.  (my original post in this thread)

                I tried to recreate this in my local machine in Tableau 10.2 and 2018.2 versions. This is a drill-down worksheet from a main dashboard, so I tried hard-coding different input values on the drilled-down worksheet/stored procedure/SQL queries and tried to visualize. This re-creating of issue took a while to figure out how, because the issue simply happened after publishing only. And surprise surprise: In Tableau 10.2 I could see the error but NOT on Tableau 2018.2. I completely re-did my code in 2018.2 and used multiple input values, the report was rendered just fine. So there's my fix.

                Unfortunately, I cannot publish 2018.2 code to 10.2 server, so only when our server is upgraded to the latest Tableau version, this issue can be ultimately fixed for the users!

                 

                I also tried another intermediate fix in 10.2 version, but it doesn’t work. There was one column whose data type was chosen randomly by Tableau (this is not the column being passed as input in the URL, but its returned by a stored procedure as the data-view). In Dev this column was being set as Number (Whole), in QA and Prod it was being set as String whereas the actual column is a DATE. So I did the following steps as per standard Tableau recommendations.

                1. I manually set the data type as Date for this new column in Data Source tab.
                2. In my stored procedure when no data should be returned("0" is passed as an input) I set the dummy output to be returned as NULL for this column .So SQL explicitly knows this is NULL defaulted value when no data is returned, not defaulting a string or a number.

                 

                Regards,

                Vinitha.