Hi all,

I'm in the middle of testing the upgrade of an FM3 database to FM9 and I'm running in to some web form problems. I am getting Field not Found errors with a handful of the fields in this database. There's nothing obvious to these fields - the non-working ones are similar to the working ones. All of the fields (working or not) are text and part of the same table. I tried switching to some of the other layouts in the DB, but no luck there. A couple of the non-working fields have custom value lists (yes/no), but since the web form is submitting values to match those on the lists, I'm not sure if I have to do anything or not.

I'm kinda outta my element here (server admin - not much of a coder), so any assistance would be greatly appreciated. Thanks!

-Dave

More information is needed to seriously troubleshoot your problem, but a few things to come to mind.

• The fields you're trying to write to are not on the layout you specified in createRecord() (or your search if you're performing an update).
  
  
• The problem fields are in a related table and you didn't specify the name of the table reference in the field name ("table_ref::field_name")
  
  
• You have a typo in the problem field names.
  

It also sounds like you are not making API specific layouts

A couple of the non-working fields have custom value lists

This is a recipe for slow load times. You should build API specific layouts containing only the fields you need to access via the API. You should only link a field to a value list if you want to utilize the list in the API.

Edited November 21, 200817 yr by Guest

Thanks for the response! Building a new layout resolved almost all of the problems. The final one was a very subtle typo on a field in the DB - the author had an extra space between a letter and an underscore.

Also, thanks for the heads up on the custom value lists. I'll work on disassociating them once I've gotten this iteration working.