Hello,
A client is willing to add 500 field to a template.
Please advise.
Regards.
Hello,
A client is willing to add 500 field to a template.
Please advise.
Regards.
Even if it's possible this is probably not a good idea from a user experience perspective. Why do they think they need 500 fields in their template? Is there really that much data associated with each document?
The users will be using weblink to access the forms . But all the fields must be searchable.
Hi Guillaume,
This situation sounds very interesting. Do you mind me asking, why are there 500 fields? It sounds like you might be combining serval metadata standards or on very large one. Can you elaborate?
-Ben
Hi Ben,
The client want to have all the metadata of forms stored in repository. The fields must be available for search.
We are talking about bank applications forms fro a corporate entiry, where there might be about 50 signatories, each of them have their addresses and we have basics of the form, applicant name, name of company in case of corporate application.
Users will use web link to search. they must have option to search by signatory name, applicant name, entity name and so on...
--Guillaume
Are you familiar with multi-value field groups in version 10.2? They can make it so that you don't need a separate set of fields for each signatory.
Please see KB 1012452 regarding system limitations. It states
Number of fields per template schema - 999
And while that may be the case, I would also re-examine the customer's use case to see if there may be a better way to handle their metadata.