Is there a limitation in Forms where Lookup values cant be stored to metadata? If I put another field's output in then it works fine. As is it wont save anything.
Laserfiche Forms Version 10.0.0.1154
You should check the field width for the field in question in the admin console.
Good thought but the field is 40 characters wide in Admin console.
*The value is stored on the form itself which is saved as a tif
Forms only save the value you filled in the field into repository. The list options won't be save to the repository. For example, if you select "Test 4" for lease name it is put in the textbox, then "Test 4" will be value in the LeaseName field for the metadata.
So I should open a support case if it will not store any value from the lookup list to metadata?
Forms doesn't support save all the values returned by lookup into Repository. If you want the metadata field in repository have same list as Forms, you can use the Dynamic Fields feature in repository to populate the field with values from same column in same tablehttps://www.laserfiche.com/support/webhelp/Laserfiche/9.2/en-US/AdminGuide/LFAdmin.htm#Dynamic_Fields.htm
Ben, if I understand you correctly, yes, you may want to open a support case.
Forms should be storing the specific value selected for that field back to Laserfiche, as long as the submission is successful and it's not violating any constraints on that field. So, for example, if you selected "Test 4" as shown in your screenshot, "Test 4" should be saved in the field value in Laserfiche.
I'm not familiar enough with Forms to suggest a troubleshooting process, but since you've already confirmed that other values can be stored to that field, it looks like submission is successful.
I realized that the variable assigned to the metadata field had the correct name but that field in the form had been deleted. The variable assigned to the Form field did not match the current name.
Not sure if thats a bug or feature request but it would be easier if the Forms field names/variables would update when they are changed or removed.
Thanks!
Hi Ben, it's hard for Forms to know whether the variable used in Save to repository is still valid or not because it doesn't know what exact variable the user want to use. For example, like in your case, variable1 is used in Save to repository at first, but the field linked to variable1 is deleted and variable2 is a replacement of variable1. But Forms can't tell it should update to use variable2 in this case. So it's rely on end user to tell Forms what variable should be used.