Quick Search Value List Error

Yahoo Archive
1
No I'm in 9.  905.701 to be exact.  Is it a bug in 9 as well?  Any relatively easy fixes or should I avoid using value lists in my quick searches?
2

I'm making a quick search, and one of the criteria is a value list.  I want this criterion to be optional (ie. the sales guys can either select an option from the list or not select one).  However, when I leave the "Filter on Null" checkbox unchecked, and I don't select an option when quick searching, I get the following Application Error:


"Failed to enable constraints.  One or more rows contain values violating non-null, unique, or foreign-key constraints."


Checking the "Filter on Null" checkbox prevents the error from occurring, but it essentially makes the criterion required.  I tried changing the condition from = to >= to Matches, and I added a "Quick Search Value Item" with a null value member, but neither of these prevented me from getting the error when the criterion is left null.


Anyone had experience with this before or have any ideas?  Thanks.

3
If you are in 10, this is a known bug I've ran into a lot.


Jose C Gomez
Software Engineer


T: 904.469.1524 mobile

Quis custodiet ipsos custodes?

On Tue, Sep 15, 2015 at 9:47 AM, tyler123452@... [vantage] <vantage@yahoogroups.com> wrote:

 
<div>
  
  
  <p></p><p>I&#39;m making a quick search, and one of the criteria is a value list.  I want this criterion to be optional (ie. the sales guys can either select an option from the list or not select one).  However, when I leave the &quot;Filter on Null&quot; checkbox unchecked, and I don&#39;t select an option when quick searching, I get the following Application Error:</p><p><br></p><p>&quot;Failed to enable constraints.  One or more rows contain values violating non-null, unique, or foreign-key constraints.&quot;</p><p><br></p><p>Checking the &quot;Filter on Null&quot; checkbox prevents the error from occurring, but it essentially makes the criterion required.  I tried changing the condition from = to &gt;= to Matches, and I added a &quot;Quick Search Value Item&quot; with a null value member, but neither of these prevented me from getting the error when the criterion is left null.</p><p><br></p><p>Anyone had experience with this before or have any ideas?  Thanks.</p><p></p>

</div>
 


<div style="color:#fff;min-height:0;"></div>