Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 6997 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

I have a layout which has email addresses. When the user does a find request entering the first characters of an email address it returns nothing. Is there a problem when the field has special characters such as '@'. There is a similar problem with web URLs.

What am I doing wrong?

Posted

@ means joker char in finding. You should add sign to indicate @ is not typed as joker char

Your seacrh criterion sholud be "@".

Adam Djuby

Posted

That is not my question ... the user is not searching for the @ part of the address. For example one record has a email address like [email protected]

Usually the user would enter a query with the following in the field:

"abc". This works in other fields but it does not find anything for this find.

Entering "abc*" does find the record, but this is not necessary in all fields. What is the difference?

Posted

Hmmm ... in the process of generating a test file, I discovered that the find worked in the data file. But it didn't work in the UI layout where the find is done via a script.

Investigating this further, I see that I defined the field in particular as a calculation field, but incorrectly had defined it as a number. For some reason, this worked sometimes but not for some finds so that misled me.

Thanks for making me look closer at it. Problem solved

This topic is 6997 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.