Skip to main content

You are not authorized to access this component (40,20)

Hello,

If you get error like You are not authorized to access this component (40,20) then you can look at your roles and codes which related with transferred pages and permissions.


Firstly, check the role if the role has permissions for peoplesoft menu like bellow;

select ROWID,A.* from PSAUTHITEM A where MENUNAME=<Page's Menu Name>

CLASSID
MENUNAME
BARNAME
BARITEMNAME
PNLITEMNAME
DISPLAYONLY
AUTHORIZEDACTIONS
TEST_ROLE
ATTND_MENU
USE
ATTND_INSTR2
ATTND_INSTR2
0
4
TEST_ROLE
ATTND_MENU
USE
ATTEND_INST_1
ATTND_INST
0
14
TEST_ROLE
ATTND_MENU
USE
CLASS_ATTENDANCE_I
CLASS_ATTENDANCE_I
0
2

Check AUTHORIZEDACTIONS field and update this field as 4 for selected rows.

If you use Transfer function in a page, check your transfer code's parameter and make sure your parameters must be same with result of select statement. Panel name is name of your page. For instance if my page name is ATTND_INSTR2 then I type transfer code's parameter like bellow;

Transfer( False, MenuName.ATTND_MENU, BarName.USE, ItemName.ATTND_INSTR2, Page.ATTND_INSTR2, "U", DERIVED_SR.DESCR, STDNT_ENRL.EMPLID, STDNT_ENRL.ACAD_CAREER, STDNT_ENRL.INSTITUTION, STDNT_ENRL.STRM, STDNT_ENRL.CLASS_NBR);

On the other hand you can get this error even if you don't use transfer function in your codes. When you get this error, make sure if your component name and item name fields are not same. If it's same, probably, you'll get this error.

Delete your page in PIA. Open Application designer and your component. Change your page's item name in component page than register your component again. Most likely, you'll see your page again.

Loves,

Comments

Popular posts from this blog

pg_ctl: command not found

Hi, If you can not reach pg_ctl command in bash also you are sure this command exists in your server, check $PATH. -bash-4.2$ echo $PATH /usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin So, the directory of pg_ctl is not seem in PATH. Input directory of pg_ctl and check it then run it.

PostgreSQL Foreign Data Wrappers

Hi all, I would like to mention about generating Foreign Data Wrappers(FDW) on PostgreSQL 9.6. FDW is used for remote access to tables from external data storage. If needed to use remote table in a query, you can use FDW tables. For instance you can get a table from remote database, but there is a condition. The condition is that user should have proper privileges on FDW table. There is two extension for FDW on PostgreSQL. First one is used for accessing PostgreSQL database to PostgreSQL database, called postgres_fdw . Second one is used for accessing PostgreSQL database to different databases (SQL Server, Sysbase) called tds_fdw .  Foreign Data Wrappers feature lets you to cross-query between remote database tables. Postgres_fdw and tds_fdw has different structure. Tds_fdw usign Tabular Data Stream application layer protocol to transfer data between database server and client. Generating Tds_fdw and Postgres_fdw is similar. I share an example for generating FDW between two Po

PostgreSQL High Availability - Patroni 2

Patroni kurulumuyla ilgili oldukça fazla kaynak bulunmakta fakat kurulum ve yönetimini beraber barındıran kaynağa denk gelmedim. Bu yazıda hem Patroni kurulumu hem de kurulum sonrası yönetimiyle alakalı detaylara ulaşabilirsiniz. PostgreSQL cluster'larının yönetimi için kullanılan Patroni ile ilgili temel bilgilerin yer aldığı Autofailover üzerine hazırladığım yazı serisine aşağıdaki linklerden erişebilirsiniz. PostgreSQL ve Autofailover PostgreSQL'de Autofailover ve Patroni 1 (Giriş) PostgreSQL'de Autofailover ve Patroni 2 (Kurulum, Konfigürasyon ve Yönetim) PostgreSQL'de Autofailover ve Patroni 3 (Mevcut PostgreSQL Cluster'inin Patroni'ye Geçirilmesi) Patroni, PostgreSQL veritabanlarının kurulumundan ve konfigürasyonundan sorumludur. Yani Patroni'yi kurduğumuz sunucular aynı zamanda Patroni ile kurulmuş PostgreSQL'leri barındıracak. Üç node'lu PostgreSQL ve üç node'lu ETCD cluster'larını oluşturacağım. Kuruluma önce üç no