As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at firstname.lastname@example.org and provide your corporate email address, company, and name.
The being drilled to is part of the URL that is created from the drilldown portion of the stylesheet. This is what you see when you hover over a link that can be used for drilldown where it says IBIF_ex=fexname. also identifies the domain, when there is one.
As for the fex being drilled from, you would have to program that explicitly by passing a parm (&var) in the drilldown that identifies the calling fex.
In FOCUS since 1991 WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex WF Client: 77 on Linux w/Tomcat
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007
Guessing that you are using a 7.6.x release - please update your profile so we don't need to guess - you can run an "Impact Analysis" on a stand-alone procedure from the Reporting Server Console -> Procedures.
Right click on the procedure name and select "Impact Analysis" this will tell you if the procedure is called by any other procedure in your APP PATH.
Not sure if there is a similar search for Managed Reporting.
WebFOCUS 8.2.03 (8.2.06 in testing)
Posts: 253 | Location: Melbourne, Australia | Registered: February 07, 2007