problem: the user cannot see all the values on his prompts, but a brand new user with the same rights can. report written in BO FC 5.1
symtoms: list of prompts cannot be refreshed when the user opens BO FC 5.1 report on webi 6.5
the object is a filter
filter name: Annee/Mois ?
where: @Select(Periode de connexion\Annee/Mois) IN @Prompt('Choisissez une ou plusieurs periode','A','Periode de connexion\Annee/Mois',MULTI,FREE)
reason: bug
solution: create a new user, copy the personal reports of the old user to this user and delete the old user.
lundi 17 décembre 2007
vendredi 7 décembre 2007
Locked General Supervisor
This saved my life today.
If you don't have a second general supervisor, you could try the following SQL run against the security domain database:
Code:
Update OBJ_M_ACTOR Set M_ACTOR_C_PASSWORD = NULL Where M_ACTOR_C_NAME =;
This will set the password for the general supervisor to null, and therefore the next time you login, you will not need to enter a password. It is recommended that a password is given asap via the supervisor module. You will also have to set the status of the user login, otherwise even with a null password BusObj will not let you log in. The status column is in OBJ_M_ACTOR and is called M_ACTOR_N_STATUS. If you set this flag to 1 along with setting the password to null then you should be okay. If this still doesn't work, make sure you have commited the database update
If you don't have a second general supervisor, you could try the following SQL run against the security domain database:
Code:
Update OBJ_M_ACTOR Set M_ACTOR_C_PASSWORD = NULL Where M_ACTOR_C_NAME =
This will set the password for the general supervisor to null, and therefore the next time you login, you will not need to enter a password. It is recommended that a password is given asap via the supervisor module. You will also have to set the status of the user login, otherwise even with a null password BusObj will not let you log in. The status column is in OBJ_M_ACTOR and is called M_ACTOR_N_STATUS. If you set this flag to 1 along with setting the password to null then you should be okay. If this still doesn't work, make sure you have commited the database update
Inscription à :
Commentaires (Atom)
