Hi there, @rosekherr… you didn’t need to deploy in order for us to see your editor, you just needed to provide a link to the editor itself. That being said, we can use the name of your app to create a link to your editor, and I took a look under the hood.
After poking around a bit, I’m pretty sure the custom states you are setting when the search button is clicked (especially the one on the search button itself) are causing the behavior you are seeing. However, you can accomplish the desired results without the custom states, so I will throw the following out there as food for thought.
Keep the not found group as not visible on page load, and remove the conditional on that group. Also, you don’t necessarily have to have the repeating group inside another group; you can keep it visible on page load because it won’t show anything until a search is performed. Finally, the workflow on the search button would be configured as follows:
- Hide the not found group (probably not necessary but can’t hurt just in case it is visible when the search button is clicked)
- Display the list in the repeating group (you don’t need any conditions on this step)
- Show the not found group only when the repeating group’s list count is 0
I tested what I wrote above, and it seems to produce the desired results while simplifying things a bit. Want to give it a shot and see if it works for you? If you need any help getting it working, I would be happy to provide screenshots from my test.
Hope this helps.