We have been using a lookup table for many customers who are separated via separate indexes. The table is simple but drives our device dashboard data using a customer_id_tok for dropdowns. Each customer has a different prefix e.g 1100001 (customer A) and 1500002(customer B) on the lookup. However we have devices that have written to two or three indexes over time as we have reused the devices for different customers when fixed. This now seems to have caused a problem on individual customer dashboards as they can see the "customer_id" which is for another customer in the lookup as the device historically was linked to another "customer_id" Is there anyway of segregating via the token or some other way so that the dashboard dropdown can only see say customer_id's prefixed with say 11 or their matching prefix? ... View more