LAE

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: SSP

Hi - I need to run some graphs on a weekly basis and I enter some date in "run parameters". I run the graph and save it, the data is saved but the "run parameters" don't save when I re-open the graph. My colleague do the same thing and everything is saving properly but not for me. Is there someone that would know the reason. thanks in advance.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: andycooper

Are you running the desktop version or the server version?

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Patman

I am encountering the same problem, but with Parameter 1. Every time I update the values of the parameters then I re-open the graph, I see the old parameter values. However, the new parameters I've created will be there as well. I'm using the server version.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: stonysmith

I'm not sure what you mean by "the new parameters are there as well".
- Which version (4.x.x or 5.x.x) of LAE are you using?
- If you're on 4.x.x, try clicking File/Force Save. See if that saves your parameters.
- Make sure that the matching BRP for your BRG file is not set to read only.
- Do you have more than one copy of the BRG open at once? You should only open a BRG in one window at a time.
- Is the BRG file on a network drive? Does some other user have it open also?

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: xathras

SSP.. All my resources have the same problem. I've seen this issue in 4.1.8, 4.5.3, 4.5.4, 4.6.0... This is known to many people including a few people I know in services (Larry, Ernest, Rocco). Lets hope this gets fixed and SSP yes its blooming annoying..!!!

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: stonysmith

I am aware of two specific cases where Run Parameters might not be kept:

1) If I have multiple Runs (Graph/RunManager), and I switch back and forth between several Runs, making changes without getting out of the RunManager screen. In this case, sometimes the parms are not kept.
answer: Click Graph/RunManager, select ONLY the one Run you want to change, change any parameters you wish, but then click OK to close the window _before_ going back to Graph/RunManger to change another Run. (Change only one Run at a time - don't bounce between them) It also helps a bit if you select the Run you want to modify from the main toolbar before you go to the RunManager.

2) If I import a BRS, a new "Prod_Recovered" (or similar name) Run is often created. That Run may have blank (or old) parameters on it, because they aren't properly stored in the BRS.
answer: Personally, I tend to delete any "*_Recovered" runs in my graph when I find them, and often, I delete such Runs before I import a BRS.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: ejones

I just wanted to chime in here.
Yes. I've seen this. Doing what Stony says here will reduce the time invested in entering run parameter values and losing them by either allowing you to catch the issue sooner and possibly reducing the likelihood of it occurring.
Just for the record, I have seen this occur when populating just one run parameter value in the current run.
I've spent time trying to find the steps to reliably reproduce this issue without any success.