EntityIDSelector in Acumatica: What It Is and When to Use It
1. What is EntityIDSelector
EntityIDSelectorAttribute is a special attribute in Acumatica that allows displaying a universal selector field for any entity by its NoteID.
The main feature is the ability to uniformly select any record in the system, regardless of the module (AR, AP, CR, etc.).
Why is it needed
EntityIDSelector is useful when:
· You need to store a reference to any entity in a single field while supporting autocomplete and descriptions.
· You need a universal linking field for different object types (e.g., customer, vendor, employee).
· You are creating custom logic that works with different document types and want to provide users with a single selection interface.
2. Usage Example (Acumatica 25R1)
Now I want to give a basic example of how it works. Suppose we want to create a RelatedEntityID field that can refer to any counterparty (Customer, Vendor). In fact, we will have one field, but depending on the selected type, it will change its behavior.
Let's create the necessary extension fields for the Sales Order:
Also, for this example, we need a graph extension where we will dynamically change the type:
After adding these fields to the UI
<px:PXTextEdit runat="server" ID="CstUsrRelatedEntityType" DataField="UsrRelatedEntityType" />
<px:PXSelector runat="server" ID="CstUsrRelatedEntityID" DataField="UsrRelatedEntityID" CommitChanges="true" AutoRefresh="True" AutoGenerateColumns="True" AutoRepaintColumns="True" />
You will see that when selecting the document type "SO," our “EntityType” field is set to Customer, and the “RelatedEntity” selector will display all customers.
ut if you change the type, for example to "QT," the “EntityType” field changes to Vendor, and the “RelatedEntity” selector will display all vendors.

Thanks to the additional “EntityType” field storing the type, we can fully control the selector’s behavior.
EntityIDSelector is a powerful tool in Acumatica that makes the interface more flexible and user-friendly. By allowing you to store a reference to any entity type in a single field, it simplifies logic, reduces unnecessary fields, and provides users with a consistent, unified data selection mechanism.
If you are working on customizations that require combining multiple entity types under one selector, EntityIDSelector is exactly what you should consider using.