The Dynamic view panel control does not have the "ExpandLevel" property so how get the views displayed in that control expanded by default?
As usual, thanks for your input
There is an ExpandLevel property in the 'data' properties (All properties tab).
Data > data > expandLevel property:
Related
I have a process that involves extending the "Files" menu that is located on (most) acumatica pages (next to notes and activities in the top right)
I would like to add two columns to the table that appears in the smartpanel.
I have been looking for the source code/data behind this smart panel and I cant seem to find it, is it tied into SM202520 (search in files)? Can it be extended?
Am I better off just adding a PXAction button to the 3 or 4 pages I want my extended "files" menu to be?
Thanks
There's no DataView bound to that dialog, you can verify that by using inspect element shortcut key CTL+ALT+CLICK on a grid column header:
In order to be customized the grid needs to be bound to a DataView which inspect element reveals it is not. The lack of DataView binding is by design and therefore that dialog can't be customized.
A grid that can be customized will show the View Name property:
I have a dataview control from the ExtLib and it is categorized. However the categories are expanded by default. How can I set this to collapsed?
I have seen code for the viewpanel control, but this does not apply to the dataview control.
Try setting the expandLevel property to 1 on the view data source:
<xp:dominoView ... expandLevel="1">
I've told a view to open using an XPage, but how do I open that XPage in edit mode?
I will suggest that you buy and read the Mastering XPages book to learn the basics of handling views and documents in XPages. The book contains material that describes exactly what you are looking for (how to open an XPage in read and edit mode).
I will assume your question relates to the XPage being used to open the selected document from the view and not the view itself as it is not possible to either define an XPage to to launch a view or for a view to be in "Edit Mode"...
When specifying the document data source for an XPage it is possible to define the default action as being Edit Document or Open Document. This sets the "action" property of the data source
The XPage itself has a "readonly" property that can be set to a specific value or computed. This is not tied to a specific data source.
It is possible to add a panel container control to the XPage and set the "readonly" property of the panel. This will allow all the controls inside the panel to be rendered as editable or readonly.
views and xpages cannot be in edit mode, only document data sources can be in edit mode.
In addition to the readonly properties that Peter mentioned:
It is possible that a custom control got its own data source while the one from a parent (e.g. the xpage) is in edit mode. That's the mistake i make often while binding controls to data fields.
I have a custom web part that has custom properties. To Edit the properties I have a custom EditorPart.
I need these properties to be able to be exported with the webpart. To do so I have to set the WebBrowsable attribute to true which makes the custom properties show up twice in the editor pane once with my editor part and my custom validation and once automatically.
Is there a way to get the properties to export with out setting WebBrowsable to true?
You might want to try setting the ExportMode property of your WebPart
There is a good explanation on MSDN here
http://msdn.microsoft.com/en-us/library/system.web.ui.webcontrols.webparts.webpart.exportmode.aspx
I created a custom control with a custom property. The property type is String and the Editor is Control Picker.
When I place the CC on an xPage and try to set the property the editor displays just fine, the only issue is that it seems to only list the controls on the CC and none of the controls on the xPage.
Is anyone else seeing this issue?
There is another editor in the list called the 'XPage Control ID Picker' this editor will list all the controls in the higher level XPage that the custom control is on.