Is there a way, in InfoAssist, to add a single leading zero ...

[NYCBabak .]

Create a Reporting Object and put the SET command in the preprocessing. Then have users create their reports using the Reporting Objects instead.

There are very few SET commands available in InfoAssist but I think the RO alternative opens a lot of doors to those of us who need to fine tune the reports with SET commands. Alternatively, if this is going to apply to all reports, why not set it in the edasprof

[Douglas Lee 2]

@nycbabak, Thanks, but were not using ROs

[NYCBabak .]

Then you can put it in the edasprof.

[Douglas Lee 2]

edasprof: What a concept. Well check that out as an option. Although that sets it for everyone, not just one or a select few users

[NYCBabak .]

You can also have user based profiles but its a little more complex. I cant think of any reason your user population would be that upset if this was the default. Its purely cosmetic.

[Douglas Lee 2]

Is there a way, in InfoAssist, to add a single leading zero as is accomplished adding SET CENT-ZERO=ON in text editor The middle image shows the desired result. The top is 'normal, the bottom appends the L to the format (not acceptable).

[Ilias .]

If you do not mind having an additional FEX then put all the SET statements, DEFAULT values, etc., in a manually created FEX. Then Include the report created in the InfoAssist. This will eliminates altering InfoAssist report manually and adding values to the edasprof.

[NYCBabak .]

Theres no -INCLUDE in the InfoAssist GUI.

[Ilias .]

I agree that we cannot -INCLUDE in the InfoAssist. My suggestion was to include the InfoAssist report inside a manually created FEX doing the preprocessing.

Ex,

SET PAGE-NUM=NOLEAD

SET SQUEEZE=ON

SET CENT-ZRO=ON

-INCLUDE IBFS:/WFC/Repository/xyz/InfoAssistReport.fex

[Douglas Lee 2]

Hi There @ilias.basha Unfortunately these are Advanced Users with IA Only create/edit roles, not Developers.

Dont get me wrong, I like all these ideas from the vast experience coming thru on this

[Eran Arigi]

please see later notes

[NYCBabak .]

Continental Decimal Notation, CDN, sets the decimal separator as a comma and the thousands separator as a period. Im afraid thats not what Dougs asking for.

[Eran Arigi]

Hi

Youre right, I mixed up the two,

I can suggest the following method which is more customizable: try and set it in WF Client site.wfs conditionally,

If the user saves all these reports which should display CENT-ZERO=ON in a specific folder in BIP or use a naming convention when saving the procedure which would indicate he wants to use this feature.

In WF Client admin console -> client settings -> site profile you could add

-INCLUDE to a fex

In this procedure which runs every time a report is being executed you could add different tests so for example use Dialogue Manager to test IF &IBIMR_domain contains the name of the folder then SET CENT-ZERO=ON else it would be OFF.

or if the fex name for example contains czero_on you can set it behind the scenes for the user.

A list of available parameters can be retrieved by:

- &

The advantage of this method is that you can utilize various variables which exist on the WF client side during runtime,

If you wish to use &IBIMR_domain then you have to export it,

MR_BASE_DIR should also include the full path and fex name.

In WF client admin console- custom settings: use the SET command in-between <>

SET IBIMR_domain(pass)

SET MR_BASE_DIR(pass)

Then in the included fex in site profile you could use the following:

-DEFAULTH &CENTZ=OFF

-DEFAULTH &MR_BASE_DIR=

-SET &CENTZ=IF &MR_BASE_DIR CONTAINS czero_on THEN ON ELSE OFF;

SET CENT-ZERO=&CENTZ

I hope this helps,

Yours,

Eran

[Douglas Lee 2]

Thanks Eran Arigi, Thats really in depth, but, a consideration