I played around with this concept in PS Query a bit. What I have managed to make work is to create a "free form" drilling URL on the Union and then simply providing NA as the URL. It is, however, still a clickable link, and tries to utilize PeopleSoft's URL prefix with /NA at the end. If you wanted to get fancy, you could link to a Google Doc or similar that explains that the future dated row doesn't yet exist.
------------------------------
Scott Nishizaki
Developer/Analyst
Azusa Pacific University
------------------------------
Message from the HEUG Marketplace:------------------------------
Find, Review, and Engage with Higher Education-focused solution providers, products, and services using the
HEUG Marketplace.
------------------------------
Original Message:
Sent: 08-06-2025 09:20 AM
From: Andy Roberts
Subject: "Placeholder" Expressions for Drilling URLs in Unioned Query
Hey Scott, the dummy field should work as initially described if you use the same field type in the expression. Part of what the error does NOT tell you, is that you ALSO have to have the dummy field be a drilling url. You can add any drilling url you want, but if you don't have it, you will continue to get this error. I came across this myself a few months back, and it was a major pain to figure this out.
Hope this helps!
------------------------------
Andy Roberts
Business Analyst
State of Minnesota
------------------------------
Message from the HEUG Marketplace:
------------------------------
Find, Review, and Engage with Higher Education-focused solution providers, products, and services using the HEUG Marketplace.
Original Message:
Sent: 08-05-2025 11:10 AM
From: Daniel Labrecque
Subject: "Placeholder" Expressions for Drilling URLs in Unioned Query
Yeah that is probably because although the logic exists in Query Manager, the fields themselves in the SQL are not clearly stated.
Try either CAST(NULL AS VARCHAR(##)) for characters where ## is the length or CAST(NULL AS NUMBER) for numerical fields. Let me know if that works.
------------------------------
Daniel Labrecque
Senior 2 Business Systems Analyst/Functional Architect
University of Nevada-Las Vegas
------------------------------
Message from the HEUG Marketplace:
------------------------------
Find, Review, and Engage with Higher Education-focused solution providers, products, and services using the HEUG Marketplace.
Original Message:
Sent: 08-05-2025 11:00 AM
From: Scott Frey
Subject: "Placeholder" Expressions for Drilling URLs in Unioned Query
Thanks Daniel.
Recall that when creating dummy expressions to act as placeholders on the Union level, both the Field Type and Field Width must match the corresponding column on the Top level.
What do I use for Field Type and Field Width when trying to match a Drilling URL Expression?
I've already tried:
CHAR1 ' '
NUMBER1.0 NULL
Both options return the ORA-01789 error, which is different from the usual Oracle 37,1 error where the number of columns don't match between levels. So, it looks like Oracle is reading the number of columns correctly. But mismatching on either Field Type or Field Width, or expression syntax, or some combination of the three.
------------------------------
Scott Frey
Senior Data Analyst - Human Resource Information Systems
University of Colorado System
------------------------------
Message from the HEUG Marketplace:
------------------------------
Find, Review, and Engage with Higher Education-focused solution providers, products, and services using the HEUG Marketplace.
Original Message:
Sent: 08-04-2025 05:38 PM
From: Scott Frey
Subject: "Placeholder" Expressions for Drilling URLs in Unioned Query
TL:DR
- Is it possible / How do I create:
- A "placeholder/dummy Expression" on the Union level of a PS Query, for a Drilling URL Expression on the Top Level of the query?
Details:
- Existing PS Query has a Drilling URL Expression used as a field (acts as a hotlink to a component page in HCM)
- I need to add a Union level that returns future-dated data
- The Drilling URL doesn't work for future-dated employees since the component page doesn't exist for them yet
- Therefore, the Drilling URL is acting as a de facto filtering criteria
- If I "just don't add the Drilling URL to the Union level", I get "ORA-01789: query block has incorrect number of result columns"
- Can I create a placeholder/dummy Expression on the Union level so the total number of columns is equal to the Top Level?
- If so, how?
Please advise.
------------------------------
Scott Frey
Senior Data Analyst - Human Resource Information Systems
University of Colorado System
------------------------------
Message from the HEUG Marketplace:
------------------------------
Find, Review, and Engage with Higher Education-focused solution providers, products, and services using the HEUG Marketplace.
------------------------------