Help with REST API `emails` filter
Hey all! I just upgraded to
v0.30.2
super excited to start leveraging some of the new features!
I'm working through updating my automations that talk to Twenty, and have a question about how to currently query on the new emails.primaryEmail
and emails.additionalEmails
fields.
I'm hoping to search all email fields for Persons to see if the email exists or is known or not. So I'm planning on using the or()
operator with the /rest/people
endpoint to query to see if they exist.
This filter query is working for primary emails just fine, but hoping to leverage similar to a contains()
operator for the additional emails field:
emails.primaryEmail[eq]:[email protected]
Curious if this PR is related or adds the functionality that I'm hoping to use - https://github.com/twentyhq/twenty/pull/6862
I briefly looked through GH issues but didn't see much related to the new array field type just yet for v0.30.
TIA!GitHub
Introduce ARRAY field type by gitstart-app[bot] · Pull Request #686...
This PR was created by GitStart to address the requirements from this ticket: TWNTY-6447.
This ticket was imp...
1 Reply
Found a related GH Issue - https://github.com/twentyhq/twenty/issues/7188 and https://github.com/twentyhq/twenty/issues/7262
GitHub
Implement filter on composite sub fields that contain arrays · Issu...
Scope & Context Follow-up of #6425 We implemented filtering on composite field types like ADDRESS and LINKS. The problem is that we still have to implement filtering on their subfields like sec...
GitHub
Ex:
additionalEmails
spec'd as object(key value pair) in PATCH, P...Bug Description additionalEmails property is defined as an object in the PATCH and POST definitions in the API documentation when an array is required for it to render in the GUI. Additionally, if ...