Is there any specific reason for not implementing multiple values for a single property? #584
-
I was using flipt for A/B testing, and I noticed that you have to add same property multiple times, like in my case I wanted to give only 15 users access to a new feature, and I have to add 15 properties named email, to accommodate that. Is there any specific reason we can't have an array/list of users against same property like shown below. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Would you mind sharing either a screenshot or subset of the export that contains the feature/fields in question? I'm wondering if there isn't a simpler way to accomplish what you are trying to do |
Beta Was this translation helpful? Give feedback.
Would you mind sharing either a screenshot or subset of the export that contains the feature/fields in question?
I'm wondering if there isn't a simpler way to accomplish what you are trying to do