Reserved Field Names?

asked on February 19, 2018

I was onsite with a client of ours last week and ran into some interesting scenarios when troubleshooting a Forms and Client issue.

The Forms issue was when we were trying to save a form to the repository and populate the template data. There were a number of fields assigned to the template, but the two causing issues were named 'Approved By' and 'Submitted By'. When we tried to have Forms populate those 2 fields it would not. It would save the form into the repository with all the other field values populated. Once in the repository, we could populate the fields without any problems. We changed the names of the 2 fields and were able to successfully save values to them from Forms. Once we changed them back, it didn't work again.

The other issue comes when trying to add a field as a column in the Windows Client. The field name was 'Document Name'. The field did not show as an option to select from when viewing the different fields.

So the questions is, are there reserved names that cannot be used when creating fields?

1 0

replied on February 20, 2018

For the Forms issue, I just tested this out on 10.3 release and couldn't reproduce the issue. I have metadata fields 'Approved By' and 'Submitted By' and successfully saved Form field values into those both when those fields were in a template and when they were by themselves. Did you make sure to reconfigure your save to repository task after renaming the metadata fields?

0 0

View 3 previous replies

replied on February 20, 2018

Yes, we reconfigured each time a change was made. I'll have to see if I can recreate it again and get version numbers.

0 0

replied on February 20, 2018

Do you remember what the error was? Did it just skip the fields?

0 0

replied on February 20, 2018

There was no error message in either case. When trying to assign the field values it just didn't do it.

When trying to select the field as a column in the client, it just wasn't available to choose from.

0 0

replied on February 20, 2018

If you go to the Forms instance and look at the variables list, is there a value in whatever variable you were saving to these two fields?

Or are you using system variables? If so, which ones?

0 0

replied on February 20, 2018

Yep, we checked that as well. The variables we were using to populate the fields did have values. They were not system variables.

1 0

replied on February 20, 2018

Then at least for the Forms case, I'd suggest either changing the field names or opening a support case so they can help troubleshoot your issue directly. What you are doing should work.

0 0

Question

Question

Replies

Sign in to reply to this post.