Search element glitches in next-gen

Hi!

Excited about the potential with next-gen Knack, but it seems there’s a few gaps from the classic version that I’m hoping are on the radar to be fixed. Is this forum the best place to flag things I experience?

I’m creating an app with a search element that I want to work in a similar way to this example: How to Access Private Records Without a Login. I’ve encountered these issues:

  1. The next-gen search element doesn’t have “match type” options to only bring back exact results, for example. This is a blocker to returning private records without a login (ie. by requiring the user to provide a unique password/reference), although it seems to work if I swap into classic mode & change the match type there. I’m hesitant to rely on this workaround incase something changes in the background?
  2. The “actions” feature for the search results table doesn’t register when you select an action to add. You can see from the screenshots below that I’ve clicked to add actions a few times, but it didn’t feel like anything had happened. When I tested the search I realised it had actually created the buttons… but there’s no way to edit the buttons appearance - or even delete them!

Hi @James16

Thanks for the post. You can post here, create a support ticket, or fill out this form.

I’ve created a high-priority ticket for the Search issue - for Text Formula fields, we need to include the “Contains any” or “Exact Match”.

It seems that Next-Gen is treating this as a “Contains any” if it is not set explicitly in Classic like you found. It should continue to work with that setting, but it would be best to not have to do that.

For the Actions feedback, we have work planned so that the when you click on of those items, you are scrolled over horizontally so you can see those fields. To edit or delete those field, you can hover over them and click the pencil icon or the delete icon.

Here is a video showing how to do that - Kara's video 🤓 — Tella

Thank you for letting us know!

Kara