We do all of our coding in the Content Repository (previously known as Managed Reporting).
We have a new ReportCaster 'Preprocessing' procedure stored in an application folder on the Reporting Server.
I would now like that preprocessing procedure to -INCLUDE one of our procedures in Repository Content.
The procedure to be -INCLUDEd is small and sets amper variable based on system variables, and still I would prefer not to have two copies to maintain going forward.
I've looked at the BIP 8105 manual and see it shows how to -INCLUDE a reporting server procedure in a Managed Reporting Procedure, but not the other way around.
I feel that this might have been discussed in FP before, but the search facility is not showing me any likely suspects.This message has been edited. Last edited by: FP Mod Chuck,
You should be able to navigate to the file you want to include, right click it and select properties. Then where is shows Full Path, right click on the full path value and select copy.
Then you can just paste that value after the -INCLUDE.
In this case it would be:
-INCLUDE IBFS:/WFC/Repository/Public/Procedure1.fexThis message has been edited. Last edited by: Hallway,
You cannot currently include a fex in the repository from a fex in the reporting server.
I would suggest creating a fex in the repository that calls your reporting server fex, and also have an include of your amper variable fex in it and have ReportCaster run that.
If a report existing on the reporting server is run, it only has access to fexes on the reporting server.
IF a report existing in the repository is run, it is scanned for all includes (and those scanned as well) and the fexes are "shipped" to the reporting server and then executed.
If you have amster files set up for the repository, you can extract the fex. But this assumes that the fex does not have includes, otherwise you woul dhave to scan it and then pull those fexes as well.
Yes, I did try the WebFOCUS IBFS path, but no dice.
It is, as if, the reporting server doesn't know about the IBFS.
Your comments make perfect sense.
The only code we have on the reporting server are when ReportCaster requires it, e.g., preprocessing procedures/distribution lists.
It will pretty unlikely that these fexes (fexi?) will need to include repository focexecs. In my current case, it wouldn't be a large issue to copy up the one fex.
Once again, many thanks.
Ah-ha... I learned something new.
|Powered by Social Strata|