Amplify-cli: Unable to search on enum field with @searchable

[jorge-riberi]

Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the
Amplify Console GitHub Issue Tracker

Describe the bug
It is not possible to search in an enum field, the transform does not construct the search query with that field.

Amplify CLI Version
4.12.0

To Reproduce
Make a @model and @searchable type, add a enum field type, and build.

Expected behavior
The enum type field were included

[VicFrolov]

Any updates on this?

[idanlo]

+1

[cheunjm]

+1

[jakemitchellxyz]

+1 - enterprise blocker, any workarounds known?

[henryyuhsiufeng]

+1

[andrewandyle]

+1

[edwardfoyle]

Hi all, we understand this is a pain-point and will prioritize accordingly but we can't commit to a timeline for the fix at this point.

In the meantime, the workaround is to modify the generated search query to include the enum in your schema.

[mmiermans]

@edwardfoyle We don't want to change generated code files, so we copyied the Searchable FilterInput to our schema.graphql:

1. Copy the generated input called SearchableFooBarFilterInput from build/schema.graphql to your schema.graphql. (Where FooBar is the name of your model.)
2. Copy all *FilterInput dependencies of the above input as well.
3. Add myEnum: SearchableStringFilterInput to the SearchableFooBarFilterInput in schema.graphql.
4. amplify push

This unblocks us, but obviously the workaround is not great in the long term, so I appreciate that you're prioritizing a fix in Amplify.

[clodal]

On our end, we worked around this issue from the application layer by creating a proxy string field to replicate the enum field value.

Order @model @searchable {
  paymentStatus: OrderPaymentStatusEnum!
  paymentState: String! # Proxy for paymentStatus to enable filtering on searchable

I share the same sentiments with @mmiermans on this issue.

This unblocks us, but obviously the workaround is not great in the long term, so I appreciate that you're prioritizing a fix in Amplify.

Thanks!

[casendler]

+1 - facing the same issue and would expect enum types to behave like string input types when it comes to sorting/filtering

[JtawRobot]

• 1

[eripoll]

+1
I think I will go with the Proxy solution but it's a pain.

[mikerudge]

+1

[edeuxk]

+1 please fix it team :-)

[asmiki]

+1

[deepaksingh007]

+1

[alexboulay]

+1

[yonatanganot]

Hey @edwardfoyle.
Do you have good news to share with us about this missing feature?

[PaulCailly]

+1