All,
I just came upon a need to disable several hundred logins. Last year, I was able to do it quite handily using a ‘user management \\ username’ import . (i.e. category: 'user management' ; import type:‘username’ ).
Since BBID, this import no longer exists, so I was informed that I must instead use a ‘Contact Card-Import/Refresh \\ General User’ import and set the ‘disable_login' column to ‘Yes’.
But the CATCH seems to be this only works in the flavor of import that uses the host_id; not the flavor that uses user_id. (sure enough, the ‘disablelogin’ column is missing from the user_id flavor)
I tried it by using sticking a host_id in a record and the import worked: it disabled the account.
But since we don't generally use hos_tid, it looks like I'm gonna have to jam some [unique] values for all my records simply to do this import.
Is there a reason for this limitation? It seems to impose an extra layer of work for no good reason and a bulk operation like this could cause problems. e.g. How do I ensure uniqueness in the host_ids? The only safe approach I can think of is to jam each record's userid into the host_id but this seems a little wonky if not downright dangerous.
Has anyone run into this? And is there any reason for this restriction?
Thanks.
