Hello - this is my first post here so please bear with me. We are currently working on making ReportCaster available to our users and have run into an issue with the Task Parameters default. I was wondering if any of you have found a workaround for this (I have a ticket in with IBI and they are looking into it as well, but I wanted to check here to see if anyone knows of a workaround in the meantime).

Our organization has HTML pages linked to procedures. The user selects their parameters from the HTML page, and it passes these values to the linked procedure. When testing ReportCaster (via the Schedule Report button that we added to the HTML page using HTML Composer), we are seeing that in the Parameters tab, under Parameter Properties, there is a box checked by default which says "Always Use Default Value Specified in the Procedure". We are trying to find a way to have this box unchecked by default - we would like the procedure to use its default values only when the user has not specified a value. As of right now, our workaround is going to be to have the user uncheck this for every single parameter when setting up a schedule (obviously, this is less than ideal).

As I mentioned, IBI is researching this for us, but we want to make sure we're exploring all options - if any of you have found a way to have this checkbox unchecked by default, I would greatly appreciate your advice on this.

We are on 8.0.02M.

Thank you,
Christie

This message has been edited. Last edited by: ChristieH,

I have 7.7.03 it is unchecked be default...Can someone else confirm that?

In case anyone else on 8.0.02 is having the same problem -- I heard back from IBI and they advised that this issue has been corrected in 8.0.07, so it seems that it may just be specific to 8.0.02.

I have asked to see if they are able to provide me with anything to correct the issue in 8.0.02 and will update this thread once I receive a response back.

Thank you for checking your version, Prairie - I guess it was changed in 8.0.02.

IBI was able to reproduce the issue in 8002 and advised us that we need to upgrade in order for this to function as desired. I have updated the thread as CLOSED.