6 Replies Latest reply on Apr 17, 2017 8:01 AM by csoto

    Blank Queries On Workspaces Since Upgrade To LDSD 2016.4

    Tristan Apprentice

      We have recently upgraded our Service Desk installation to 2016.4 from 2016.0

       

      The upgrade was fairly smooth however we have noticed that reports on Workspaces have started to display blank. These queries did not start out as blank and were functioning correctly for a certain amount of time. If i jump on self service as SA and modify the query or delete the query and add the query back to the window it works but then another query on the same Workspaces page will go blank!?

       

      If i fix the query above by modifying it or adding it back to Workspaces then the query below goes blank!?

      Report Template under Process for My Current Activity:

       

      <table style="width: 100%">

        <tr>

        <td colspan="3"><font face="verdana" size="2">

       

       

      <img src='{Status/_Image3}' width="593" height="23"></font></td>

        </tr>

        <tr>

        <td colspan="2" style="width: 767px"><font face="verdana" size="2">

         <strong>{Lifecycle/Class/Title} Id:</strong> {Id}</font></td>

        <td><font face="verdana" size="2">

        <strong>Summary:</strong> {Title}</font></td>

        </tr>

        <tr>

        <td colspan="2" style="width: 767px"><strong>Logged:</strong>

        {CreationDate}</td>

        <td><strong>Last Updated: </strong>{LastUpdate} by {LastUpdateUser}</td>

        </tr>

        <tr>

        <td style="width: 767px"><strong><font color = "green">{_AssignmentDetailsCalc}</font></strong>

        </td>

        <td style="width: 767px"> </td>

        <td></td>

        </tr>

        </table>

       

      Report Template under Configuration Item for "My Devices"

       

      <table style="width: 100%">

        <tr>

        <td><font face="verdana" size="2">

      <strong>Name:</strong> {_DisplayName} <br> <strong>Model:</strong> {_Model} </font></td>

        </tr>

      </table>

       

      Does anyone have any idea why this might be happening? This is happening on both our live and test servers.