Please, does anyone know if and how I can hide a field in a master file, preventing it from being captured in a reporting object.

Thank you.

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

Is it possible to hide a field?

Try to leave the fieldname empty, but let the alias in place with the correct name. Did not try this lately, but in historic versions this would not show the field in devstudio. Might be that it will now also leave it out of the list for reporting object fields.

Here is the master file example but it's not working. Both fields(AMOUNT1 & AMOUNT2) are showing in infoassist report:

FIELDNAME=AMOUNT1, ALIAS='Net Amt %', USAGE=D8.2%, ACTUAL=D8,
MISSING=ON,
TITLE='Net Amount %',
PROPERTY=MEASURE, $
DEFINE AMOUNT2/D8.2% = AMOUNT1 * 10;,
TITLE='Net Amount %', $

is there a way of making AMOUNT1 not to show in infoassist report?

Thanks.

As I said, this was the way to hide fields in the 'old' days. Apparently that does not work anymore. I have no idea how to do prevent fields from showing up in IA. Maybe opening a case with this question will give you a definitive answer.

There's an attribute called INTERNAL you can put on your MFD. I 'hid' our social security number field, then defined a new version with the formatting:

FIELDNAME=C_SSN, ALIAS=C_SSN, USAGE=A11, ACTUAL=A11,
MISSING=ON, ACCESS_PROPERTY=(INTERNAL),
TITLE='SSN', DESCRIPTION='This field is INTERNAL becuase we defined SSN as formatted', $
DEFINE SSN/A11 =IF ENTITY_MASTER1.ENTITY_MASTER1.C_SSN GT ' ' THEN EDIT( C_SSN, '999-99-9999' ) ELSE '';
TITLE='SSN', DESCRIPTION='Social Security Number', $

Hi Mike,
I am getting error with your sample code. Am are doing anything wrong? Pls, check the code below:

FIELDNAME=AMOUNT1, ALIAS='Net Amt %', USAGE=D8.2%, ACTUAL=D8,
MISSING=ON, ACCESS_PROPERTY = INTERNAL,
TITLE='Net Amount %',
PROPERTY=MEASURE, $

DEFINE AMOUNT2/D8.2% = AMOUNT1 * 10;,
TITLE='Net Amount %', $


Does wf recognise ACCESS_PROPERTY?

Mike,
Never knew this existed - I'm still of the old-school. But it works like a charm. Thanks, great tip!

@umun: you do have to put the INTERNAL keyword within (), otherwise it won't work, as you noticed.

Yes, it's working now. Thanks guys.

I am actually looking to do something very similar in my MFDs. Which manual is this located in? I have a feeling I'll need to look at some of the more esoteric options and don't want to bother everyone with noob questions.

Thanks!
- ABT

The first manual I found this in is the SNF for release 761/762. Do a search in your set of digital manual for the term ACCESS_PROPERTY.