I want to hide the field labels in custom form - to provide a table like data input option. Successfully achieved by just leaving the Label empty.
But this results in Reports view showing no header for those fields.
In List View "Field" is displayed in place of label
Required Solution:
Provide additional fieldType option
"Hide Label in Form"
Checking this would not display label in the form alone. List view & Report view behave as usual.
Related
I'm facing one weird problem on the Contact entity. I do have one check box type field on the Contact form. When user selects (ticks) this checkbox at that time I'm making one field as mandatory in the BPF. This is a two options (yes/no) field on the BPF.
The problem is when on click of the checkbox on the form, the BPF field displays "click to enter" text, not sure why it is showing this text on the field.
I have created a new field in sale order line named as "Price1" and "Price_chk" boolean field in Sale order. The field "Price1" should be invisible in tree view when the field "Price_chk" is False and it should be visible when the field "Price_chk" is True.
You can not hide field conditionally in tree/list view, you can invisible but that should be fixed for all data not conditionally.
You can only set readonly and required (if treeview is editable).
Solution:
You can use two different treeview, for that you need to create two menus and two separate actions, in that action you need to specify view and domain.
Forgive my ignorance for the proper terminology, but let me try to explain what I want to happen.
I have two custom fields on the incident table/form. I have created a custom table with 2 columns. I have figured out how to reference the table in one of the fields, allowing me to search the entries. Now I want to link the field selection to the other field via the custom table I made. When I make a selection in field A, I want field B to populate with the other column on the same row Field A pulled from in the first place. How would I do that?
Sounds like you want what's commonly referred to as a "derived field" or a dot-walked field.
You have a reference field which stores the reference to the other table, and want a second field on the form that shows another field on that referenced table. You don't actually need to create a new element, you just need to add a dot-walked form element.
Once you have the reference field added, go to Personalize/Configure the form layout.
In the slushbucket of available fields, you'll notice that reference
fields show up in green text with a little [+] next to them.
Select your reference field and a little button will show up between the two
lists, just above the "Add" button
Click that button and the left-side available fields will show the fields available on that reference field's table.
From here, select that second field that you want to display on your form, and bring it over to the right side where you want it.
In the database table I have a CLOB column that stores content with html markup. To display the content, I have a "Hidden" item called P4_DESCRIPTION and in the region that I want to display the value of the item, I use &P4_DESCRIPTION. .
Unfortunatelly it is not evaluating the HTML markup and displays the content as it is stored in the DB.
I also tried to change the P4_DESCRIPTION from "Hidden" to "Display Only" but I have the same problem. A workaround that I found is that if I have the P4_DESCRIPTION as "Display Only" and in the region I keep the &P4_DESCRIPTION. then the &P4_DESCRIPTION. will evaluate the HTML code. In this case I have hide with CSS the item and I will have the result I want. But I suppose it's a dirty way of doing it.
What is the clean way of displaying the content of the column that contains HTML markup? (btw to create the content of that column I used the rich text editor field)
Set the item to Display Only and set Escape special characters on it to No.
When defining the properties of a custom control in the "Property Definition" section, you can choose as "Type" in the "Property" tab the option of "extraColumn" and "iconColumn".
How should this type be used ?
Both iconColumn and extraColumn relate to the corresponding tags of the dataView control. You would typically use these when your custom control contains a dataView and you wish to allow an outside control to pass in details about the columns to be used in the dataView.
When a data view is used in a standard XPage, the extraColumns appear as actual columns. The summaryColumn is the first column and shows as a link.
However, in a mobile application, extra columns show up as additional lines of data in the mobile data row. The summaryColumn value shows as "header" in the data row, while the extraColumn values show underneath that value.
<xe:dataView id="dataView1" pageName="#contactDetails" collapsibleDetail="true">
<xe:this.data>
<xp:dominoView var="view1" viewName="TeamDirectoryNameLU">
</xp:dominoView>
</xe:this.data>
<xe:this.summaryColumn>
<xe:viewSummaryColumn columnName="Name"></xe:viewSummaryColumn>
</xe:this.summaryColumn>
<xe:this.extraColumns>
<xe:viewExtraColumn columnName="Office" style="font-size:12pt"></xe:viewExtraColumn>
<xe:viewExtraColumn columnName="OfficePhone" style="font-size:12pt"></xe:viewExtraColumn>
<xe:viewExtraColumn columnName="Email" style="font-size:12pt"></xe:viewExtraColumn>
</xe:this.extraColumns>
</xe:dataView>
One row of that might display as:
Ian Kennedy
London Office
44-22-830-6000
ian.kennedy#company.co.uk