While back, I've created an SQL to find the exact same thing but with some level limitations. I have came across another query written by Jim's PeopleSopft Journal blog that works a little bit better and thought to share it with my visitors.
Jim's query however requires the developer to know the content reference of a component before the query could be used. What I really wanted is the ability to find the path by just knowing the component and not the content reference. Chances are, if you know the component reference you know the path to that component as well. So, to find the component path without knowing the content reference, follow the steps below:
1) Run the below SQL to get the content reference name for your component
2) From the query above - copy the value in the CONTENT_REFERENCE field and replace the ":1" variable and you will have the path to your component.
So, the 1st query is to get the content reference for a component name that you know and then using Jim's query to find the path!
| Title | Under | Posted on |
|---|---|---|
| Inserting records | PeopleSoft Technical | 07/28/2010 - 11:03am |
| WEBLIB_PT_NAV.ISCRIPT1.FieldFormula.IScript_PT_NAV_PAGELET error... | PeopleSoft Technical | 07/27/2010 - 2:02pm |
| Basic language | PeopleSoft Technical | 07/27/2010 - 7:12am |
| Rowlevel security from app designer | PeopleSoft Technical | 07/27/2010 - 5:15am |
Comments
Post new comment