TM1 Forum

Hi,

Just a quick question on the security assignments on chores in TM1. I'm wondering if what we're facing is a bug or is something we weren't aware of:

[*] We have automated the daily data uploads from source systems through TI's and chores
[*] These chores are scheduled to run automatically each night, but we have also granted access to some users to run these ad-hoc if needed
[*] When altering something to the chore we therefore need to first de-activate the schedule before we can edit
[*] After changing, saving and re-activating the schedule on the chore, the security assignments on that chore switch back to none and we have to re-assign READ access

What do you think? Is this normal / expected behaviour because of the modifications we sometimes do?
I would have assumed the security rights remain in place, regardless of changes to the chore.

Thanks,
Mathias

When a chore is edited what TM1 does in the background is to delete the old chore and register a new one with the same name. In the process any data (such as security assignments) associated with the chore are lost.

In my book this is a definate bug. However it has always been like this ever since there have been chores so IBM might see this as "expected behaviour".

Good luck getting it sorted with IBM.

In the meantime you can work around it by setting chore security with rules and looking up a fixed name(s) that you know aren't going to be deleted, I'm sure you get the idea.

Thanks for the quick reply.

It confirms what we already suspected so at least that's that.
Quite annoying and in my opinion also not the kind of behaviour you would expect (i.e. a bug) but ok.
Your suggestion regarding security rules on chores was something we were also thinking of, so that's likely the way we will proceed.

But again thanks.