Essbase security filter assginment gets messed up
Summary
Essbase security filter assginment gets messed upContent
Hello,
we are setting our essbase security using the essbase api from inside an ETL-job.
The job is calling the function "setSecurityFilterList", after deleting and re-creating the filters.
Whenever a user is dropped by "drop user **** from security file" (MAXL) or a completely new user should get a filter,
the filter assignment is not as it is supposed to be. Some users who should have the same filter as the "new" person have no
filter set anymore, others who should have another filter at once get the same filter as the "new" person, even though the
0