Problems with EIS development

[czampa]

I have been using Brio Intell for 3 years now. I have developed quite well in Query, Results and Pivots; and would now like to get strong in EIS. I am finding this to be rather difficult compared to the other sections, so I purchased the Brio Reference Manuals (following examples explicitly to match what I am trying to accomplish); still no luck. All I want to do is build limits via a drop-down box from the Results set and display the output in a pivot in the local EIS window. Are any of you strong in the EIS functionality?

 

[mpcohen]

Without seeing your code it is a little difficult to answer your question. If you want you can send me an email at mpcohen@mindspring.com.

Some general pointers. Use Active Document.Sections to reference limits, methods and controls. Everything is case sensitive and it is easy to make spelling errors.

If you do not use try/catch statements in your code (explained below) the code processing just stops as soon as an error is encountered. You can use the Alert(<srting>) command to keep track of how far your code has gotten.

You can use a try/catch for debugging. A try/catch looks something like:

try{
<your current code>
}

catch(e)
{Alert(e.toString())
}

The catch section traps errors. As soon as an error is reached the code goes to the catch section. One thing that you can do in the catch section is to display the error, as I have indicated. You could also set some variable,for example i, at various points in your code in the try section and have Alert(i) in the catch section to give you an idea of how far you got.

You can also use the console window to see what your code did.

I hope this helps.