Dynamicfield dropdown posible values limit?

[rick20]

Hello to everybody,

Problem:

We have about 1000 customers. Each customer has several (from 10 to 300) offices in different locations. I want to have statistics for each address. One of idea is customer can write address (where ticket appeared) in dynamic field (textfield). But the problem is each time he can write the same address in different, and for statistics it is not good.

I decided to make drop down field, there all customers address will be stored. For each customer will be separate ACL. When customer logins to the OTRS, only possible addresses for him will be shown.

My questions are:
1. is it ok to make 1000 ACL's?
2. is it ok to write 15000 values to dynamics field "Possible values" field?

Maybe some of you can suggest better solution for this issue.

Hope my questions understandable

[root]

This sound like a typical use case for an ACL module. This is a module returning an ACL after doing some calculations, database lookup etc. Here is an example (wo/ database queries): https://github.com/OTRS/otrs/blob/rel-5 ... dChilds.pm

[rick20]

Can you please describe this answer to me more in depth.

[root]

With some development you're able to return the correct list of values for each customer.

[rick20]

OK. It is getting interesting. Where possible values should be stored? Separate table or dynamic field?