Hi Everyone--
We have a cascading prompt for Managers and their Sales Associates.Ã, We are noticing that when we select "Reprompt" the system takes 3-6 seconds before the "Your Report Is Running" message appears.Ã, Once it appears the data is usually displayed within 1-2 seconds.Ã, We are noticing this lag in just about every scenario where a promptÃ, button is pushed.
My question:Ã, Is this lag time normal for ReportNet?Ã, We don't want to assume that we are designing something incorrectly if this is a common thing in ReportNet.
Thanks for your advice!
Aaron
If your prompts are DB driven (non-static, as most cascading prompts are) than I'd say, yes, the lag is normal and DB dependant.
Hi Darek--
I expect the time delay for a DB driven prompt but I was hoping that the message "Your Report Is Running" would occur quickly so the user would not be confused. I initially used the "Auto Postback" but I dont think that most of our users would realize that the screen was going to refresh if it takes 3-5 seconds for the message to appear. My ideal situation would be for the message to appear immediately. Does that make sense?
Thanks!
Aaron
On which table is your prompt based? On the Primary Key table (Dimension) or on the Foreign key table (fact).
You should base your prompt on the smallest (Dimension / Primary key) table.
e.g.
2 tables: Country and Orders.
In both there's a Country Code column.
In this case you should base your Prompt on the Country table and NOT on the Orders table.
Also, how many report processors do you have available? Are they fully utilized?
was this issue resolved?? can you please let me know how you made it work