Hi All,
I am on Xcelsius 2008 SP4
I get the below error message when trying to PREVIEW the dashbaord
error is: “an error occurred during SWF generation. For more info contact your admin”
this looks like a very general error message and the problem could be any thing. I tried other things like use another laptop, try reducing the range from 4000 rows to 1500 rows. these work but I need to know what else could cause this. where else to look into?
IronMan (BOB member since 2005-09-09)
welp…
what does the Maximum number of Rows say, at the following location?
File > Preferences > Excel Options.
p.s. Bringing over 1k rows in one block into Xcelsius is a very very bad idea under any circumstance. Xcelsius is not a Table. It makes SWF files.
Cairmor 
(BOB member since 2008-06-05)
The Max no. of Rows is set to 4000. I am not mapping these 4000 rows directley to any component. Instead I am using DSUM function in Excel and figuring out what user has selected for a given combo box, then using that as my criteria to look up in a sheet which has 4000 rows and get one row of data. So finally I am mapping 3rows/24cols of data to my combination chart. I know Xcelsius components cannot handle large amts of data when mapped directely, but hoped this would work perfectely. But looks like it doesn’t. disappointed that even 4000 rows are heavy to handle for Xcelsius…and clients expect this to be done in xcelsius
IronMan (BOB member since 2005-09-09)
I work on dashboards everyday that utilize datamarts with over a billion records.
Xcelsius is not the problem here.
What is your datasource? Are you comfortable using xcelsius to pass parameters into your data connectors to make smaller datasets?
Cairmor (BOB member since 2008-06-05)
my datasource is Liveroffice–WEbi reports–Universe–Bex Queries. We only need to show cached data in dashbaords, no user should hit the database while using dasbhboards.
IronMan (BOB member since 2005-09-09)
At the Webi level, you need to make a prompt on one of your high level dimensions (like State or whatever).
The arguments used will be “Matches pattern” and the default value will be * or % or whatever your database wildcard is.
The dashboard will pass a value into the prompt, thus reducing the size of the returned dataset.
Here is a real world example:
I have 150 divisions.
Each division needs 55 metrics.
Each metric will need calculated at the month period.
So, my point is…I do not bring in this entire dataset at the same time with one Live Office query.
I bring in 55 small datasets each with its own L.O. connector, that are 12 rows each (one for each month)
I make a drop down combo that sends the division name to the query via a webi prompt.
If your Bex query is efficient and running well, this setup will be very very fast.
Cairmor (BOB member since 2008-06-05)