Is there currently a way to "rotate" the orientation of a table? Not dynamically, but just to configure it that way. By "rotate", I mean with headers on the left (in the first "column") and rows displayed to the right (in the second "column" and so on).
From this:
To this:
No. This is not supported by any built-in components. :)
But you can decorate Grid (like Table does) and build this type of interface.
Related
I have an working generic inquiry and wanted to expand it by a field in a related table
The table ContainerHistory is connected to the SerialContainer by the ContainerID. And there is no reference from SerialContainer to ContainerHistory
This is the definition for the result grid and the navigation
On first glance everything seems to work correctly, but after a bit of testing I realized that the navigation to the edit-screen always takes me to the entry on top of the inquiry. Has anyone experienced something similar or can give me a hint on how to deal with this navigation error?
Are you using Grouping on your GI?
I have seen this happen when the primary Grouping Field(s) do not match the Key fields for the Inline Navigation..
eg if your keys for navigation are LotSerialNbr and InventoryID - make sure your GI is also grouped by those keys.
Introducing another table can sometimes result in duplicate records which confuses the Inline navigation (at least in my experience)
I am refactoring an old web app into React and Material-UI, and I find myself stuck when trying to find the proper way of presenting a "property table". I have looked into several data table implementations, but neither a data table nor Material-UI's List seems to be the right tool for the work.
Data tables are meant for each row having the same properties (columns) repated for different entities, whilst I need a kind of table where each row is a key+value presentation. I will call it a property table unless someone can tell me there is already a better name.
Below is a picture of current view in the refactored app (contains only test data). I realize I might need to think differently and not just copy the old structures.
So what would be the correct way to present a similar list of properties with Material Design?
I seem to find no explicit component or view type for my "property table", so I will simply make a table with Material-UI <Table>component, and skip the header.
Currently I'm using jxls and it works just fine. The basic element I use is transformXLS from net.sf.jxls.transformer.XLSTransformer class. In the template I use </jx:forEach>. The simplest use-case, I think. The question is, can I hide columns and change their order dynamically ? I see setColumnsToHide() in aforementioned class so I gues it is possible (I am not sure though), but Is it possible to change column orders too ?
EDITED:
maybe I will ask about the same thing in a different way. Can I achieve that ${el.${col.rate}} in any way ?
<jx:forEach items="${cols}" var="col"> ${col.name} </jx:forEach>
<jx:forEach items="${elements}" var="el">
<jx:forEach items="${cols}" var="col"> ${el.${col.rate}} </jx:forEach>
</jx:forEach>
*${col.rate} is the column name for el
I have core data app with an entity OBSERVATION that has as one of its attributes DEALNAME.
I want to reference through Interface Builder or by making custom modifications to an NSArrayController a list of unique sorted dealnames so that I can use them in a pop-up.
I have attempted to use #distinctUnionOfSets (and #distinctUnionOfArrays) but am unable to locate the proper key sequence.
I can sort the ArrayController by providing a sort descriptor, but do not know how to eliminate duplicates.
Are the #distinct... keys the right methodology? It would seem to provide the easiest way to optimize the use of IB.
Is there a predicate form for removing duplicates?
Or do I need to use my custom controller to extract an NSSet of the specific dealnames, put them back in an array and sort it and reference the custom array from IB?
Any help would be appreciated. I am astounded that other have not tried to create a sorted-unique pop-up in tableviews.
You need to take a look at -[NSFetchRequest returnsDistinctResults]. That is the level you need to be handling the uniquing of data.
Although I do not have a definitive answer for you, I think there are two ways you can go about it.
The way you already started. You need to bind the contents array of the PopUp button, not just against the arrayController.arrangedObjects, but continue on the path and somehow filter only objects with distinct "DealName"s. This means - the arrayController presents ALL the entities (and may sort them for you) but the PopUp button will have its contents filter via some sophisticated binding to the array controller.
Make your filtering at the ArrayController level (as suggested in another answer here). Here it depends how you set up the array controller. If It is set up to use an "Entity" (vs. "Class") which means the array controller will fetch CoreData entities directly - you can modify its "Fetch" to only bring a subset of the "OBSERVATION" entities with distinct values of "DEALNAME". I don't know how to control WHICH entities are filtered out in this case. Otherwise, you can setup the arrayController to work with "Class" objects, and then you can fetch the entities yourself (in code) and populate the arrayController programmatically, with just the entities you like.
In the second option, the Popup button should be bound normally to the arrayController's arrangedObjects.
I am trying to create a Custom Field Type in SharePoint.
This control has it's value set based on another field in the same list.
Because of this requirement, this field should be displayed only in the Display Mode, and not in the Edit or Create mode.
How do I ensure this?
If I just code the ASCX control to not render a field, the field will show up like this in the Edit and Create mode.
alt text http://www.mannsoftware.com/blog/Lists/Photos/121308_0204_CrossSiteLo6.png
Generally you set the SPField.ReadOnlyField property to True to achieve the desired behaviour for any field. (Don't forget to SPField.Update accordingly!) There is an equivalent CAML attribute for list definitions, I believe.
That said, in your control class deriving from BaseFieldControl, you might just override the RenderFieldForInput() method and not call the base implementation to ensure nothing is rendered during Create or Edit. However, this would still render the field's table row in the form, which is probably not what you want. So to enforce the desired behaviour, use ReadOnlyField and override Update() in your SPField (not field control) class to always have it set to True.
It might be easier to just change this on a list-by-list basis by going to the Advanced section of the List Settings, setting Allow management of content types? to Yes, and then editing your content type to change the value of your field to 'hidden'.
Take a look at this blog post. I think it will give you some ideas. The concept uses different rendering templates based on the mode.
http://sharepoint.nailhead.net/2008/04/creating-rendering-template-that.html
Did you try and set the field as hidden?
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spfield.hidden.aspx
Custom FORMS pages for new item and edit item (NewForm.aspx and EditForm.aspx) would be another way to achieve this.
Setting the ShowInEditForm and ShowInNewForm properties solved this for me.