Hey everybody, I inherited an instance of the reporting serv...

[Ricky Ray 2]

Hey everybody,

I inherited an instance of the reporting server with a lot of problems. Everything (all synonyms, acx files, etc) was put into baseapp. App Studio would take forever to load and navigating your reporting environment would take forever. We recreated the pertinent synonyms in a new application path which all of our reporting references in an APP PATH line of code.

So all of our reports have this kind of code

APP PATH EXAMPLEAPP

which reference the new place where all of the synonyms are at.

We also cleaned out baseapp and removed all of the synonyms and other data. Everything was working well except that existing reports that used a FIND command to populate amper autoprompt would spit out an error. Error occurred during Autoprompt processing.

So things like WHERE (FIELD EQ &PARAMETER.(OR(FIND FIELD IN EXAMPLETABLE)).Parameter.);

Even though I have the APP PATH reference in the report, it still is looking in baseapp for table referenced in the FIND command.

I can resolve this by creating a the synonym referenced in baseapp but I would like to avoid this if possible. Do I have any options

App Studio 8105m

[David Beagan]

You could put your APP PATH exampleapp in the global server profile.

or

I thought you could

WHERE (FIELD EQ &PARAMETER.(OR(FIND FIELD IN exampleapp/EXAMPLETABLE)).Parameter.);

[Ricky Ray 2]

Thank you! I think I just made an edit to the global server profile that hopefully addresses this. I noticed that it was referencing APP PATH baseapp so I added the new application path to that.

[Manoj Chaurasia]

Does you APP PATH say APP PATH exampleapp baseapp or are they two separate commands. If it is multiple commands the last one overrides the first one so it is best to reference multiple app folders in the order in which you want it to search.

[David Beagan]

And I dont think you ever need

APP PATH baseapp

 

because baseapp will always be included on the app path. Even if baseapp does not appear in any APP PATH statement, it will still be part of the app path.

[Ricky Ray 2]

Go to know! It was like that already in the global server profile, so I didnt change it (I just added my new application path to it).

@chuck.wolff I did it all on one line, not separate commands. But from what David is saying, it sounds like I dont even need the reference to baseapp in the global server profile. I will leave it as is, everything is working and I am not experienced enough with these things to feel comfortable monkeying around in the administration console.

[Toby Mills]

Hey Ricky

One more thing to add to what David has already passed along - now that you have your edasprof.prf using the new PATH, you really didnt need to add all those APP PATH statements to your individual fexes Doesnt really hurt to have them in there, just saying you might be okay to take them back out.

Glad you have it working.

[Ricky Ray 2]

Thank you all!

Is there any way that edasprof would get changed on an automatic process I changed it yesterday to reference the new path and today I go back and it is only referencing baseapp again. I really doubt anyone else is touching the file so the only thing I can think of is either A. Maybe there is some sort of process that could roll back edasprof back to its default or B. WebFOCUS gremlins

[Manoj Chaurasia]

WebFOCUS gremlins There is nothing that just updates that without someone prompting it.

[David Beagan]

I wouldnt expect there to be any roll back process. On the Reporting Servers file system, you could look at the last changed date-time to get a clue as to what is going on.

[Ricky Ray 2]

WebFOCUS gremlins left it alone overnight so maybe they have moved on. Thank you all for your help, I will mark the topic as SOLVED!