Answers.Body: <p>The difference between the old ContactReference and the new EntityReference fields is that the former uses APIv3 and the latter uses APIv4. There are subtle differences in the parameters of each. If you notice, the help text underneath &quot;Advanced Filter&quot; actually changes a bit when you switch to EntityRef and it gives you a working example of how to filter by contact type and group.</p>
  <p>For a full list of available filters, use the APIv4 Explorer (Under <strong>Support -&gt; Developer</strong> in the menubar). Any fields available in the &quot;Where&quot; clause for Contact.get can be used as filters.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-08-24T16:24:13.633Z
Answers.Text: Perfect. Thanks for pointing out the change in the fine print. This works now:
  `action=get&groups=106`
Answers.UserDisplayName: Justin657
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-08-24T13:42:47.287Z
Answers.LastActivityDate: 2023-08-24T13:42:47.287Z
Answers.UserDisplayName: Coleman
Body: <p>I'm looking to convert a few custom fields from type &quot;Contact Reference&quot; to &quot;Entity Reference&quot;.</p>
  <p>However when I convert the fields, the autocomplete &quot;advanced filter&quot; stops working.</p>
  <pre><code>action=lookup&amp;group=106
  </code></pre>
  <p><strong>BEFORE</strong><br />
  As a Contact Reference field, the advanced filter works fine and displays only the contacts in the specified contact group.</p>
  <p><a href="https://i.sstatic.net/bRkEc.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/bRkEc.png" alt="enter image description here" /></a></p>
  <p><strong>AFTER</strong><br />
  When it becomes an Entity Reference field, the autocomplete displays ANY contact of any type, totally ignoring the filter.</p>
  <p><a href="https://i.sstatic.net/jrUEV.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/jrUEV.png" alt="enter image description here" /></a></p>
  <p>I have tried playing with the advanced filter parameters but no luck. I don't see any relevant documentation.</p>
  <p>Any ideas?</p>
  
Tags: <custom-fields><entity-reference>
Title: Advanced Filter for an Entity Reference Custom Field doesn't filter by Contact Groups
ThreadText: # Advanced Filter for an Entity Reference Custom Field doesn't filter by Contact Groups
  
  (Asked by: username_0 on 2023-08-24)
  
  I'm looking to convert a few custom fields from type "Contact Reference" to "Entity Reference".
  However when I convert the fields, the autocomplete "advanced filter" stops working.
  action=lookup&group=106
  
  BEFORE
  As a Contact Reference field, the advanced filter works fine and displays only the contacts in the specified contact group.
  
  AFTER
  When it becomes an Entity Reference field, the autocomplete displays ANY contact of any type, totally ignoring the filter.
  
  I have tried playing with the advanced filter parameters but no luck. I don't see any relevant documentation.
  Any ideas?
  
  **Tags:** custom-fields, entity-reference
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2023-08-24. Score: 1 | Accepted answer
  
  The difference between the old ContactReference and the new EntityReference fields is that the former uses APIv3 and the latter uses APIv4. There are subtle differences in the parameters of each. If you notice, the help text underneath "Advanced Filter" actually changes a bit when you switch to EntityRef and it gives you a working example of how to filter by contact type and group.
  
  For a full list of available filters, use the APIv4 Explorer (Under **Support -> Developer** in the menubar). Any fields available in the "Where" clause for Contact.get can be used as filters.
  
  > **Comments:**
  > **username_0**: Perfect. Thanks for pointing out the change in the fine print. This works now: `action=get&groups=106`  
  
  ---
  
  