I used a DataSet with relations set up to display Parent/Child tables. In the Child Bands the Character Cashing MUST exactly match the DataSet. For example, the DataMember is case sensitive as well as any field names, or nothing will display.
Also, when using the designer, entering Key names does not show up in the list until you exit out and come back.
I consider both of these to be bugs that should be corrected!
Hello funpilot2,
Let me know if you need further assistance with this question.
The alignment worked, thanks.
I am using Visual Studio v 10.0.40219.1 SP1Rel
For the first issue – can you tell me what version of Visual Studio you are using?
In Visual Studio 2010 when some of the properties of the band/column are changed (Key or Header Text) they are applied both in designer and in “.aspx” code when “OK” or “Apply” button is clicked.
For the second issue – if you want to change the alignment of the text in column you have to use selectors:
<style type="text/css">
tbody > tr > td.MyStyle
{
text-align:right;
}
</style>
<ig:BoundDataField DataFieldName="Score" Key="Score" Width="60" CssClass="MyStyle">
In this forum post you can read more about text alignment - http://forums.infragistics.com/forums/t/37511.aspx
Let me know if you need further assistance about this question.
Ok, I understand the casing issue.
As for the editor, I select Edit Bands/Columns and click on the ellipse, the designer comes up, and I add or change a field and enter a key, the original setting displays in the list until I select OK and bring the editor up again.
Another issue, I want to right justify numeric columns. Under Misc I entered a CssClass (as below) in both the Misc section and the Header section for the column. The header right justifies, but the body does not.
.CellRight
text-align: right;
Hi funpilot2,
I'll address your designer problem first. I tried using the Bands editor and I see names showing up in the tree as soon as I change the key. Perhaps you could write out some steps to reproduce this issue?
As for the field names and data members being case sensitive. This has to be the case as you can have two properties with the same 'name' that have different casing. For example an object that has an int ID prop and an int Id prop. How would we know which to take. Its for that same reason we need the data member to match case as well.
regards,David Young