Hiding fields UIX_XML

Hello,
I'm working with BC4J uix-xml, I have some problems with hiding some fields.
Ex: my select is select naz_id,
naz_des,
from nazione;
I would like to hide the naz_id field but it is hidden only if I don't select it in my query in View Object.
How can I hide the field by setting only Display Hint = Hide in view attribute wizard?
Please help me, thank.

Display hints are not supported by BC4J UIX XML at this time.
To hide a specific field, use rendered="false". If you're
using automatic mode (like <bc4j:table automatic="true">)
what you probably really want is to turn automatic mode off
and explicitly add each column that you really do want.

Similar Messages

Hiding fields in HCM forms

Hi Experts,
I have following requirement for hiding fields in my form.
I have two screens MANAGER and HR screen.
now i have some input fields which has to be visible in MANAGER screen and
and should be hidden in HR screen.
please let me know how can i achieve this using form calc or java script.
any code will be helpful.
Thanks,
Santosh

Hi sushmita,
Thanks for ur reply.
The solution which you have given i have already tried but not working.
my requirement is like MGR or HR can initiate the process.
if only MGR intiates the process the solution which u have given will work.
but here i have a diff scenario.i have created separate process for HR also but im not able
to see that process on the process list.
so i have to use only one process and resolve this.whatever im writing validation is working
only when MGR initiates the process but fails when HR initiates.
Hope u got my point.any suggestions will be helpful.
Thanks,
santosh

Hiding fields in phtmlb:formLayout (new thread)

Original Thread:
hiding fields in a bsp...
What Kevin is talking about, is some special development we did for HR eRecruitement. Well, let us turn it around. They helped us, and we returned the favour. And yes, this is actually some of the more interesting bits and pieces of BSP. (Fresh meat to discuss:).
Effectively, the <phtmlb:formLayout> has two functionalities. The first is a very easy way to layout a form. The second is a way via customization to dynamically have customers overwrite the visibility/required property of each field. So the SAP puts the maximum number of fields into the formlayout, and the customer can then via customization remove some, flag some as required, etc.
(If anybody should feel like writing a long weblog on this, I will provide technical detail, plus examples offline.)
The interesting database tables are these PHTMLB_FLI* ones. Part of the agreement was that the application itself provides for a UI to update the table. Also, the application itself controls which fields are changable.
If you really want to play, look at SBSPEXT_PHTMLB, the formLayout example. In the top part, there are also a serious of dropdown listboxes. What these do, is that they update the customization tables first, before the formlayout is rendered. So what you are seeing is actually the formlayout as it has been programmed, plus then the effects of a (customer) customization on it.
Also the example shows the effect of using an XML bee to dynamically add entries into the fieldLayout (if the application added these hooks).
brian

Hallo Thomas,
No, unfortunately we never build something to also customize the labels. They HR colleagues did not ask for this :).
I first started to write you here a loong text with answers. But then I got lazy, and searched my archive mailbox. Here below is the draft input that I wrote initially for the documentation. It describes everything pretty good. (But it is draft document, never proofread again, so read it lightly!)
bye, brian
Why?
Typically when an application is developed at SAP, the developer must make provision for all possible fields of information that must be displayed and/or queried from the user. However, in specific business cases, or depending on specific country laws, all fields might not be required. Also in some cases, fields in one scenario can be flagged required, versus in another they are only optional.
The typical starting point will be a complete formlayout done during the development. On top of this a customization layer is placed. The automatic reading and applying of the customization layer is automatically done by the phtmlb fL.
What?
For each field, a default behaviour is assumed. This is the behaviour that is defined by the developer during development time. For example, it could be specified that email address must be required. During the runtime it is now possible to overwrite the default behaviour with a customization entry for the field.
The following options are supported:
As Defined: The formLayoutItem in displayed as it has been defined during development.
Invisible: The formLayoutItem is not placed on the formLayout. It is immediately removed. All following items below it, will be moved up to fill its position.
Hidden: In this case, the formLayoutItem is placed on the formLayout, but not displayed. The item reserves its slot, and an empty slot will be displayed. However, after all items have been placed on the formLayout, a row "compression" is done, whereby all rows that contain only hidden elements are removed. Hidden is important for cases where columns next to one another must align. A typical example would be name & surname horizontally aligned. If now one item is invisible before this row, the two items will not be aligned anymore. With hidden, this alignment will be kept, and we still have the benefit of empty rows been removed.
Required: Sets the required flag for the item. Label of item will be rendered an indication that it is required (usually little red asterix after the label).
Optional: Can be used to customize a required field to be not required.
Read Only: Field value is only displayed.
What is index?
Customization is stored for a formLayout under the key that is build from the BSP application namespace, BSP application name, plus the page/view on which the formLayout is placed. It is assumed that there will only be one formLayout per view. A typical example would be:
SAP/SBSPEXT_PHTMLB/FORMLAYOUTSAMPLE.HTM
In addition, a customization key must be specified. Typical examples would be to say this is the default customization for USA, or for the specific branchen Losuegn. The customization key must be supplied with the <phtmlb:fL> tag, and only then will the customization data be read from the database.
Tables
For customization there are three interesting tables.
The first table PHTMLB_FLI is completed by the developer, and defines a list of all the formLayout items that can be customized. Only for those flItems which customization is possible, will entries be made in this table. The table contains three components:
NS_APPL_PAGE This is the unique key that identies the formLayout, consisting of namespace, application and page/view.
FLI_ID Id string of the specific formLayoutItem.
COMPONENT This is software component to which development applies, for example SAP_BASIS for all BSP development work done by us.
The second table PHTMLB_FLI_TEXT is just a language dependant text table that describes each item in the formLayout.
The tables PHTMLB_FLI and PHTMLB_FLI_TEXT are not using during the runtime. They are only of interest for design time. Note that NO tools are provided to make any entries in these tables. This is considered to be in the application domain, and will usually be part of the customization process of the application.
The third table PHTMLB_FLI_CUST is the only table that is read during the runtime. It is assumed that a customization tool has made the relevant entries for this table.
NS_APPL_PAGE see above
VARIANT_KEY This is the specific customization layer that is currently active. This string is equavalent to <pthmlb:fL customizationKey>. It is used to pull a specific customization.
FLI_ID see above
MODIFIER This is the new value to apply. For the possible values, see DDIC domain PHTMLB_FLI_MODIFIER.
For an example of customization, see BSP application SBSPEXT_PHTMLB, pages formLayout.htm. In this example, the customization can quickly be set via dropdown listboxes. On each request the PHTMLB_FLI_CUST is quickly updated and then the formLayout will find the set of new customization data to use.

Hiding fields in a form

hiding fields in a Form is called what? How do I go about hiding fields in a form than having a button the user can click on to make the fields visible to fill out? Thanks Nick

The "presence" property controls the visibility of form elements.
This eseminar explains the details:
http://adobechats.adobe.acrobat.com/p87746471/
Thom Parker
The source for PDF Scripting Info
pdfscripting.com
The Acrobat JavaScript Reference, Use it Early and Often
http://www.adobe.com/devnet/acrobat/javascript.html
Then most important JavaScript Development tool in Acrobat
The Console Window (Video tutorial)
The Console Window(article)

Hiding fields in screen area 031

Hello Masters,
I have query on hiding following fields in Quality Notification screen area 031of Notification Type Q2:
1) Windows-32 bit box (big box/window under Description field)
2) Long Text icon available next to big box/window which is also available next to Description field in header
I tried 'Field Selection: General Screens' configuration under Define Screen Templates, was unable to hide above mentioned field(window) and icon.
I hope I was able to describe what issue is and will get some help from you masters.
Thanks and regards,
Devang

Use (or Create) authorization [field|http://help.sap.com/saphelp_nw04/helpdata/en/52/67168c439b11d1896f0000e8322d00/frameset.htm] and [object|http://help.sap.com/saphelp_nw04/helpdata/en/52/6716a6439b11d1896f0000e8322d00/frameset.htm], in the BAdI [check this authorization|http://help.sap.com/abapdocu_70/en/ABAPAUTHORITY-CHECK.htm] and change the INVISIBLE field and not the ACTIVE field in SCREEN structure.
- [Programming Authorization Checks|http://help.sap.com/saphelp_nw04/helpdata/en/52/6712ac439b11d1896f0000e8322d00/frameset.htm]
Inform system admin to manage those new object and field in the user roles. ([SAP Authorization Concept Modules|http://help.sap.com/saphelp_banking463/helpdata/en/5c/deaa74d3d411d3970a0000e82de14a/frameset.htm])
Regards,
Raymond
NB: The "d" of BAdI should always been in lowercase, except in statement GET BADI...

Hiding field in SAP PDF form

Hi Experts,
I am hiding a field in PDF form.
But the problem is , form reserving space for that field after field hidden.
Could any body tell how we can remove that space if we hidden the field.
regards,
subba
Edited by: Shaik Basha on May 14, 2009 2:05 AM

Hi,
You have an option in for the field you want to hide in Palettes - > Object where you have mentioned it as invisible
Instead of Invisible make it as Hidden (Exclude from Layout) so your space will not get reserved and it will not be printed on the form also..
Hope this is what you have asked for.
If not please explain the requirement more clearly.
Thanks&Regards
Sarves

Hiding fields and subforms on interactive form for WebDynpro ABAP

Hi All:
I'm new to using interactive forms and I am creating a new form for material request. I need to hide selected fields based on the value of other fields. I also need to hide subforms the same way.
I have added the formcalc script to hide the field which apperas to work. But is I remove the field value, the hidden field is not made visible. This also applies to the hiding of the subform. I have tried the code at different events but no luck. If I enter 'KINC' in the plant field, the KINC_TAX_IND is visible. But if I remove or change the value, the KINC_TAX_IND is not being made visible.
Below is the code I am using:
if ( PDF_DATA.#subform[0].PLANT.value == "KINC" ) then
PDF_DATA.#subform[0].KINC_TAX_IND.presence= "visible"
else
PDF_DATA.#subform[0].KINC_TAX_IND.presence= "hidden"
endif
if ( PDF_DATA.#subform[0].PLANT.value == "" ) then
PDF_DATA.#subform[0].Subform2.presence= "hidden"
else
PDF_DATA.#subform[0].Subform2.presence= "visible"
endif
Thanks for any help.
Jim
Edited by: Jim Bates on Jan 23, 2008 3:47 AM

HI jim,
TRY TO APPLY THE CODE ON INITIALIZATION EVENT OF THE FORM.
Madhu

Hiding fields with same name

Hi,
I have a form built in ADOBE LC Designer ES. The form has multiple pages. I have some fields with the same name and distributed across subforms. Is there a way I can hide the fields using the common name or do I have to refernece each and every field to hide it?
Thanks,
Nakul

Is the condition for hiding the fields the same in every case, i.e. a checkbox being checked? If it is, you could put the same script in each field:
if (checkbox1.rawValue == 1){
this.presence = "hidden";
You would still have to either paste the script into each field or make it a function that gets referenced in each field, but at least it would be a copy - paste rather than having to type out the path to each field.

Hiding field in ESS portal

According to our client requirement in ESS portal we need to hide the Date of birth field from Family members/Dependents component in overview screen.
In our development ESS portal we hide the date of birth field and the changes we made are reflecting in Development ESS portal but when we moving the corresponding TR to Test system the Date of birth field is not hided its looks in disable mode as shown in the attachment.
kindly provide me some solution to solve this.

Hi,
You can hide this in two ways.
01. you have do the personalization clicking right mouse and hide the filed if you have admin rights, if not ask your portal admini.
02. if this is an webdynpro application, then via application configuaration or component configuaration, you can hide the element. ask youe webdynpro consultant.
Regards,
Dinesh

Problem with Hiding fields of selection screen which is called as subscreen

Hello All,
I have problem while hiding the selection screen which is called as subscreen.
Flow of my logic:
Selection-screen with one field and three buttons CREATE,DISPLAY and CHANGE in application toolbar.
user enter some value in field and either he press change or dispaly
When change i need to call selection screen when it is in dispaly i need to stop calling this selection screen.
Upto my knowledge we can't stop calling selection screen in display mode so there is only one possibility is hiding the fields when it is in display mode.
How can i hide the fields and where i need to hide fields?
Please post some codes.
Regards,
Lisa

you can refer the sample code which i mentioned in your previous post. that will solve the problem.

Hiding fields in ALV report

Hi all
In ALV Report .The user must be able to adapt the result list (add hidden fields, remove columns) and save the layout as layout. The user must be able to select this layout when executing the selection.
the user must hide the fields and can diplay when ever he needs in ALV report

U have to use no_out = 'X'.
fieldcatalog-fieldname = 'EBELN'.
fieldcatalog-seltext_m = 'Purchase Order'.
fieldcatalog-col_pos = 0.
fieldcatalog-outputlen = 10.
fieldcatalog-no_out = 'X'.
fieldcatalog-key = 'X'.
gd_repid = sy-repid.
call function 'REUSE_ALV_GRID_DISPLAY'
 exporting
 i_callback_program = gd_repid
 i_callback_top_of_page = 'TOP-OF-PAGE' "see FORM
 i_callback_user_command = 'USER_COMMAND'
* i_grid_title = outtext
 is_layout = gd_layout
 it_fieldcat = fieldcatalog[]
* it_special_groups = gd_tabgroup
 it_events = gt_events
 is_print = gd_prntparams
 i_save = 'X'
 is_variant = z_template
 tables
 t_outtab = it_ekko
 exceptions
 program_error = 1
 others = 2.
if sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
http://www.sapdevelopment.co.uk/reporting/alv/alvgrid_enhanced.htm

Hiding field in alv

hi,
in report program using alv grid display. i want to hide some fields. i used no_out = 'x'. for that field.
but it displays the data in grid display.
i want to select from hidden fields then display the values in grid display.
please reply me.

Hai Suresh,
You declare all the field catalog in your program.
Run the report, in ALV display what r the field u want to hide those field you can choose and right click and hide it. And this layout u save as a default layout.
OR
In display click layout button and what r the field u want to hide those field move to Hidden Columns. And save the layout as default layout.
Thanks,
Durai.V

Hiding fields in PO

Hi,
While creating PO, I cannot see netprice field can any one help me to enable it and explain me to hide and enable the fields in PO.
Venkat.

Hi,
Screen layout is not only to keep the field optional or required entry It is also useful for the hide the field completely.
Please Double click the Quantity and Price in Field Selection Group in Configuration path as i mention above
Check Price and price unit as an Optional entry.
Hope it helps you.
Thanks.

Hiding Fields in Standard Program : RFITEMAR ,LDB : DDF

Hi Experts,
Am using standard program : RFITEMAR ,as per my requirement i dont need
to display all the fields in the standard selection screen,i juss want to hide the fields which
i dont want to dispaly in the selection, as there are some dependencies i dont want keep that code in active state.
can anyone pls help me/suggest me with my logic/guidance would be helpful and very much appreciated.
Regards,
Ashok.

Hi Marcin,
Thnaks for your response.
SHDO Tcode is used for Transcation Varient which is used to hide the fields
or display additioal fields in sales order.
According to my requirement i copied the standard program into a custom program
thats where am tryig to implement changes.am not sure wether that would fulfill my requirement.
do let me if know any solution /guidance would be helpful and appreciated.
Regards,
Ashok.

Hiding fields in BSP application

Hi Friends,
Iam using HRRCF_TRM_srch BSP Application, i have a requirement to hide few fields in BSP pages. Can any one tell me what BADI and what BAPI is this BSP application is triggering at the behind. so that can will enhance the BADI or modify the BAPI, without modifying BSP page or controller.
Thanks in advance
Srikanth

Hi James,
Firstly, do you need to have the hidden items on the page? If you don't, you should just delete the items. If you do (perhaps because of the calculations you need for your second question - see below), you can set them to "Hidden" fields - select each item and set the Display As setting to Hidden.
Secondly, there are at least two ways to perform calculations on fields - either using a Page Process or a table Trigger. Page Processes will work on any fields available in the session and triggers will work on the fields on a table.
Which you choose typically depends on whether or not data is likely to be inserted or updated outside of your application.
Regards
Andy

Hiding fields UIX_XML

Similar Messages

Maybe you are looking for