We have run into a problem and wondered if anyone else had had it too and how you got round it.
In a doc we would like the user to be able to select which ‘stores’ (from another db) can see a particular document. The user selects the stores and the ID’s of the people from those stores are added to the Readers field. There can be many thousand stores so the readers field would be quite possibly massive.
We have already broken the readers fields down into many smaller readers fields to get over the problem of the field limit when created via LS. However it is possible to blow the form completely if the readers fields are too big.
Has anyone had this problem and if so how did you get round it?
have you ever thought about creating groups for the “stores” and then insert only the names of these grous into the reader fields. Groups can be stored even in separate DominoDirectories and they can be “synchronized” with agents.
Don¨t knw if this could help you with your problem but give it a thought
As for the documents itself I dont know of any problems if you use several of them. I think they will have the “normal” limit of 32 Kb size as text fields.
There will be a performance issued with views, but this is something that you have to test as it depends on how your views look like and how many documents you will have.
Look at the registration template (in the sandbox) for LS code that makes new sub-groups inside a single parent group as the existing subgroups get too big.
Sarah,are all your smaller reader fields stored on the form, and are they all on one line (albeit wrapping onto multiple lines)? e.g.
[field1][field2][field3]
if you get my poor representation?
If so, try inserting a new line between each field (using the return key) as this might get around any paragraph size limitations - basically each field will then be lookwed at as a separate paragraph rather than being part of one huge paragraph.
Hoping that makes sense & is of use … kind regards … John
