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

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

Recommended Posts

Posted

I have fields that have auto enter calculations as part of their definition. In the examples I am thinking about I have a custom function that can correct accents in text field that have encoding errors. So if you enter "√ß" into a field for example it a "ç" is automatically substituted. However when i do an import the auto enter calculation which is configured to replace existing data does not work. I can obviously use calculation fields and scripts as a work around, but I would just like to know whether there is a way of resolving this without going to that extreme. Would anybody be able to give me some pointers here ?

Posted

Try to uncheck the Do not replace existing value checkbox under the auto-enter tab for your target field.

Posted

Thanks. But is is already unchecked as that is precisely what I want to do — replace the existing value. It does this normally when I commit manually entered data, but not on an import. Is that as weird as it seems?

Posted

Perhaps obvious but when you import you do check the option to perform the auto-enter correct?

If you cant get it to work then please post a copy of your file.

Posted

Great thank you. It was obviously the obvious. Which I couldn't see for the trees. Sorry for being a dummy. Thanks once again.

This topic is 4609 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.