title: Siebel sorting not working (but it does in database)
body: <p>So I was working on a Siebel change a client requested and had to test whether it worked fine. Since we weren't given permissions to edit certain things from Siebel itself, we had to go directly to the database (some records became read-only).</p>
  
  <p>We have an Applet that listed the user's "Actions" in a view. Prior to modifying data from the database, the sort worked fine. You could enter a record and then it became read-only. I accessed the database and modified the dates for testing and to my surprise, Siebel no longer sorted the list correctly. The database (SQL Server) sorted just fine by date, but Siebel would do the following.</p>
  
  <h2>Date sort (shown in Siebel)</h2>
  
  <ul>
  <li>10/20/2014</li>
  <li>10/25/2014</li>
  <li>10/18/2014</li>
  <li>10/17/2014</li>
  <li>10/16/2014</li>
  <li>10/15/2014</li>
  </ul>
  
  <h2>Date sort (shown in Database)</h2>
  
  <ul>
  <li>10/25/2014</li>
  <li>10/20/2014</li>
  <li>10/18/2014</li>
  <li>10/17/2014</li>
  <li>10/16/2014</li>
  <li>10/15/2014</li>
  </ul>
  
  <p>Not only is this restricted to the applet itself but to what Business Services retrieve. We checked in the applet and BC but could not find any sort specification or any code of the sort that could cause this. It's like the sorting order depending upon that date field is cached in Siebel.</p>
  
  <p>Any ideas on why this could be?</p>