This is my first time developing a guided report. I'm required to allow the users to select sum fields that are computed. I read that computed fields can not be included in the double list box. The calculation has to be done at the group by level - which they will be able to select too. What I'm trying to find out is how others have handled this. I know I must probably do some sort of HOLD table with the computes in them, just don't know how to get the user selected "group by fields" in this hold table.

This message has been edited. Last edited by: <Kathryn Henning>,

Cathy,

Could you give an example with the CAR file of what you want to achieve?

Currently, there is a limitation in the Report Painter that prevents you from including a COMPUTE among the list of summed fields.
One possible work around is to create the basic guided reports with only database and define fields.

Then after you have imported the report into the HTML Composer you can go to the double list box control for the Sum fields and manually add your COMPUTE statement there.

Note that you can place the COMPUTE (name, format and formula) in the synonym, and reference it in your TABLE request as simply

COMPUTE name;

(omitting the equal sign!).

Yes, you can. However, even if the COMPUTE is in the master file although you can use it in a TABLE request you still cannot include it in the Verb Object parameter list.

On the other hand, as you mentioned by having it in the metadata when you modify the double list box in HTML Composer you only need to add:
COMPUTE name;

as opposed to:
COMPUTE name/format = complex logic;

That's what I was driving at.

Thanks so much everyone for responding. I did figure out a work around but I like the suggestions and think I will it a try.

Hi so I tried your suggestions of only including database fields in my sum double list control then going in and added the computed field to the double list box manually in the HTML composer. When I run the report from the HTML page it tells me can't find the computed field. So I get that the HTML page is calling the fex and so I'm assuming because its call the fex and the field isn't in there is can't find it....so what is my solution? I'm sure I'm just missing something silly here.

Thank you for your help.

Also, I tried to add the computed field to the .mas file which I had no problem adding. But when I use that table in a procedure I can not see the computed field. Is there some setting that needs to be changed in order to make this computed field visible in a fex?

Hi CathyB,

Please open a case for this issue on InfoResponse Online.

Thanks and regards,

Kathryn

Hi, has there been any progress on this problem? I've just run into the same thing. I need COMPUTEd fields in my parameterized report.

quote:

Originally posted by Mike in DeLand:
Hi, has there been any progress on this problem? I've just run into the same thing. I need COMPUTEd fields in my parameterized report.

EDIT - I worked around it by making a variable that contains the word NOPRINT, and put that on my launch page. I can't re-order the COMPUTE fields, but at least the fields can be put on or removed from the report.