Uploaded image for project: 'Service Packs and Hot Fixes'
  1. Service Packs and Hot Fixes
  2. MNT-16447

A Share search facet filter of type d:date returns wrong result in Advanced Search


    • Type: Service Pack Request
    • Status: Open (View Workflow)
    • Resolution: Unresolved
    • Affects Version/s:, 5.0.3
    • Fix Version/s: 6.0.N
    • Component/s: Share Application
    • Labels:
    • Environment:
    • Bug Priority:
      Category 2
    • ACT Numbers:

      00673378 00781955 00774093 00928333

    • Story Points:



      A search facet defined as d:date is not converted from UTC/Zulu time to local time in Share so returns the wrong result.

      Customer reported this on 5.0.3
      Reproduced on

      Steps to reproduce:

      1. Open Search Mananger and create a new Filter with the following values (http://host:port/share/page/dp/ws/faceted-search-config)
      • Set Filter Name to Audio Release Date
      • Check the box to Show with Search Results
      • Set Filter Property to audio:releaseDate (Release Date)
      • Save
      1. Upload a file called TestFacet.txt to the repository
      2. Add the Audio(audio:audio) aspect to the file
      3. Edit properties and set the release date to 21/06/2016 and Save
      4. Confirm in node browser that audio:releaseDate, type (d:date) is set to 21 Jun 2016 00:00:00 with the local timezone designator, GMT+0100 (BST) in my test
      5. Open advanced search and search for TestFacet.txt
      6. Look for the Audio Release Date filter. It will show the UTC datetime 2016-06-20T23:00:00Z
      7. Notice that the hit counter is accurate.
      8. Click on the Filter. 0 results are found
      9. The filter URL has the following release date value: releaseDate|2016-06-20T23%3A00%3A00Z
      10. Change this to releaseDate|2016-06-21T00%3A00%3A00Z and rerun the URL to get the correct result

      Expected Behaviour

      The face date should match the date shown in the Node Browser for the same property

      Observed Behaviour

      The value shown for the facet value does not match the property value originally set in the Node properties

      Analysis to date

      The local time set for the node property is converted to UTC when inserted to the database. When the value is retrieved for the facet value, its not converted back to local time for the filter. The same behaviour can be seen using a d:datatime facet. The hit counter is correct so seems to be based on a separate query.


          Issue Links



              • Assignee:
                shareteam Share Team
                mtunmer Mark Tunmer
              • Votes:
                4 Vote for this issue
                13 Start watching this issue


                • Created: