When working with the embed token generation and the customdata field, we encountered a limitation of 256 characters for the customdata field. If the field is bigger, the token generation is failing.
For our RLS business needs, we would like to filter on several fields, with several values and it is exceeding 256 characters.
1) Is there another way to achieve secure dynamic RLS filtering in a different way than using customdata field ?
Here is what is stated in the documentation but I would like to double check: "The only way to have dynamic RLS (which uses dynamic values for filter evaluation) in Azure Analysis Services, is using the CUSTOMDATA() function."
2) Is there plans to improve the customdata field in the token ? For example, making it bigger and/or allow several fields instead of just one. I would even consider this a bug since the field is defined as a string in the documentation.
My suggestion, as an example, would be to use 5 fields of 2048 characters: