I have a pretty basic XLF file. Has 3 sliders for 1) Loan Amount (user can select in increments of $50k between low of $50,000 and high of $5,000,000, 2) Interest Rate between 2.5% and 20.0% in increments of .25%, and 3) Years 1 to 25 in increments of 1.
Then I have a basic 1 bar stacked graph that displays the Cumulative Interest over the Loan Amount and the total of the 2 colors in the stacked graph represent the total of the loan that will be repaid over the life of the loan in years.
Everything functions correctly and the numbers and calculations have all been verified accurate for several combinations of slider changes.
But now I just tried to incorporate the Local Scenarios button so a user can save their choices. So to test this, I slid all 3 sliders to the very top and saved it as “Test1”. Then I slid all 3 sliders to the very bottom and saved that scenario as “Test2”. I have another button on my page to reset the 3 sliders. I clicked the reset button to put the 3 sliders back to their default values (which is $750,000, 9.00%, 20 years). I then tried to load scenario Test1 and it almost looked like it tried to load the scenario values (i.e. the scenario settings that I had saved), but it blinked so quickly that I couldn’t tell and all values on my screen were still set at the defaults. I then tried to load scenario Test2 and the same thing happened.
By default Adobe saves these flash scenarios as shared objects with upto 100KB size and if it is more than that, you should see a pop-up showing the local storage options asking user permission.
I tested this on my very basic SWF model where I’ve been able to successfully load a saved scenario. I used the current time (0914 - where it was 9:14pm) as the file name and when I searched my harddrive I found 2 SOL files with the date/time modified of 9:14pm (file name matches as well). I then reloaded the saved scenario just to make sure it would still work and it did just as it had previously done.
So back to my somewhat more complex model (which really isn’t very complex at all). I waited a couple of minutes and then when I saved a scenario I gave it the current time for the file name (0916 for 9:16pm). When I search the same folder as where the above SOL files were found for 9:14pm, 2 new SOL files popped up with the date/time modified of 9:16pm. Upon reviewing the file name as well, it was the one that I had just created. So it appears that it is saving/creating the SOL files correctly.
So at this point, here are the differences that I’m aware of and hopefully this is getting me closer to resolving why my saved scenario isn’t loading (or at least why it’s not displaying the values that I had asked it to save in the scenario file “0916”).
Here are some facts about these 2 SWF models in case this info helps as well…
Basic SWF file: Is not/has never been connected to Excel (never uploaded a source file from Excel). SWF file size is 189kb.
The more complex SWF file: Is a normal model with Excel source data loaded into it. SWF file size is 418kb.
I will test a new scenario - again very basic, but this time I will connect some Excel data to it to see how it reacts.
I’m really frustrated as to why my SWF model that I built won’t load saved scenarios as I have several hours of work into it already so if anyone has any additional advice based on any of this new info it would be greatly appreciated.
I am having this same exact problem, it is a dashboard built in 4.5. The scenario button saves correctly, but when I try to load a saved scenario, the saved numbers blink briefly and then everything gets set back to default (initial) starting conditions.
When I opened the same 4.5 dashboard in Engage 2008, without making any modifications, the scenario button worked perfectly. Unfortunately as you may know opening 4.5 in 2008 caused a lot fo other things to stop working/need to be tweaked, and that is not an option, this dashbaord needs to stay in 4.5 format.
If anyone has found the solution to our problem, I would love to hear it! Thanks
I have not resolved the issue but I did find a compromise solution. There was a “play” button being used on the dashboard as a makeshift “Reset” button (this is 4.5, remember). I deleted the play button and it started working. I dunno…
(BOB member since 2007-01-25)