Excel - to CI - Compile error - User Defined Type not defined.

When using ExcelToCI on Windows 10, trying to load template or stage and submit data, it gave a 'Compile error' that reference to Visual Basic code reference to DOMDocument object. 

Users usually get a "Compile error: User-defined type not defined" error

This not an error in the Windows 7 OS, it is an issue with Windows 10. More corporate users are now moving the Windows 10 as the support earlier OS is coming to an end.

More users are facing the issue with the Excel-to-CI on there Windows 10 system. There are multiple solutions on different blogs to update the code (which works).

For easy access, I have attached the complete template for 8.54 and 8.55 (and Above) tools versions to the user the Excel to CI template for the Windows 10 OS.

This is provided by Oracle and it works fine in both old and new OS.

0 comments  

PSQuery Performance issues with Rowlevel Query Security Tables


PSQuery Performance issues with Query Security Tables


We see PSQuery having bad performance due to many Query Security Join tables that the PSQuery tool adds to the PSQuery SQL for security.


We have few options to work around to easily improve the performance without much involving tunning from the DBA perspective which can time consuming.

 If security is not required for this query 

 Change the Query type to 'Process'. Process queries override the automatic row-level query security logic that is applied to all other types of queries.
   
    It will be useful for the PSQuery in Pagelet specific to the logged-in users where security is not important.

   If you are using Campus Solution and you don't know Campus solution specific query tables, you don't need Security to join tables.

 If Security is required

  Select the Security optimization checkbox, it will eliminate duplicate security.
  if still, more than one Security join tables are added and need improvement in performance, 
  one security join should be fine usually and for other records view of the table without security join table.

0 comments  

Identify navigation in PeopleSoft by a Process name or a Job name

Identify navigation in PeopleSoft by a Process name and/or Job name


There are many SQL statements in different blogs to identify the navigation for a process.
But I have modified that to get the Navigation for a Job.
Single SQL works for both Process and Job.


SELECT DISTINCT RTRIM( REVERSE ( SYS_CONNECT_BY_PATH(REVERSE (portal_label), '>-')) ,' >- ') PATH
      FROM PSPRSMDEFN
     WHERE portal_name = 'EMPLOYEE'
       AND portal_prntobjname = 'PORTAL_ROOT_OBJECT'
START WITH portal_uri_seg2 IN (
                       SELECT DISTINCT pnlgrpname
                       FROM ps_prcsdefnpnl
                       WHERE prcsname = UPPER(:1)
                       UNION
                       Select Distinct PNLGRPNAME
                       FROM PS_PRCSJOBPNL
                       Where PRCSJOBNAME = UPPER(:1) )
CONNECT BY PRIOR portal_prntobjname = portal_objname;


Hope this will be useful.

0 comments  

SQL to Identify detailed Security access for a Page or Component.

SQL to Identify detailed Security access for a Page or Component.


When you want details about a single page in the component.

select a.menuname,a.barname,a.baritemname,rc.rolename, rd.descr , a.classid, c.classdefndesc,a.Displayonly,ac.pageaccessdescr
from psauthitem a, psclassdefn c, psroleclass rc, psroledefn rd, PSPGEACCESSDESC ac
where a.pnlitemname = :1
and a.classid = c.classid
and a.classid = rc.classid
and rc.rolename = rd.rolename
and a.Authorizedactions = ac.Authorizedactions
Order by rc.rolename;


When you want details about a component.

select a.menuname,a.barname,a.baritemname,rc.rolename, rd.descr , a.classid, c.classdefndesc,a.Displayonly,ac.pageaccessdescr
from psauthitem a, psclassdefn c, psroleclass rc, psroledefn rd, PSPGEACCESSDESC ac
where a.BARITEMNAME = :1
and a.classid = c.classid
and a.classid = rc.classid
and rc.rolename = rd.rolename
and a.Authorizedactions = ac.Authorizedactions
Order by rc.rolename;

0 comments