I need to add a secondary (header) row to my ASP.NET GridView (which is already customized so I can access any part of the event lifecycle).
It's additional data that I want aligned with some of the columns.
It should look like this
Period | May | June | July | Aug -- Header
Basevalue | 3000 | 1500 | 1200 | 4000 -- EXTERNAL DATA
---------------------------------------
Item 1 | 100 | 200 | 300 | 400
Item 2 | 100 | 200 | 300 | 400
I managed to add a row with below code, but I am unable to create any kind of custom event where I could gain access and write my custom data into that cell. I tried the following, but during any event I could find (like OnRowCreated or PrepareControlHierarchy), it's either too late (after databinding) or the inner table is not initalized.
int rowIndex = 0;
GridViewRow secondHeaderRow = new GridViewRow(rowIndex, -1, DataControlRowType.Header, DataControlRowState.Normal);
secondHeaderRow.TableSection = TableRowSection.TableHeader;
foreach (DataControlField col in this.Columns)
{
TableHeaderCell cell = new TableHeaderCell();
cell.DataBinding += new EventHandler(OnHeaderCellDatabinding);
secondHeaderRow.Cells.Add(cell);
}
InnerTable.Rows.AddAt(rowIndex, secondHeaderRow);
How can I hook up to the GridView lifecycle to write in the header row?
hey niles,
we can use the caption to some HTML tags and start building the extra headers
please refer this link for your problem
CLICK HERE
hope it will help you
Try this. Merging columns in GridView/DataGrid header
Related
Assume I have the following table in DDB. One hashkey (Lets call it 'Name'), one range key (lets call it 'Activity'), and one attribute (lets call it 'Date')
|---------------------|------------------|------------------|
| HashKey(S) | RangeKey(S) | Date(S) |
|---------------------|------------------|------------------|
| Sam | Fishing | 2019 |
|---------------------|------------------|------------------|
| Sam | Kayaking | 2019 |
|---------------------|------------------|------------------|
| Peter | Kayaking | 2019 |
|---------------------|------------------|------------------|
I want to do a conditional save on this such that I want to add a new "name + activity" and keep the most up to date date in the DB. So a breakdown of the 2 possibilities would be
1) If there is an existing hash+rangekey already based on what I have passed into the save, I want to check my condition expression and not update if it fails.
2) If it is a new hash+rangekey, I want a new row to be created, and not check my condition expression (since there are no values in the table to check on)
An example of what I tried
public void methodToDoSave() {
final Map<String, ExpectedAttributeValue> expectedAttributes =
getExpectedAttributes(date);
final DynamoDBSaveExpression saveExpression = new DynamoDBSaveExpression()
.withExpected(expectedAttributes);
mapper.save(dbItem, saveExpression);
}
private Map<String, ExpectedAttributeValue> getExpectedAttributes(
final Date date){
final Map expectedAttributeSetupForConditionalUpdate = new HashMap();
expectedAttributeSetupForConditionalUpdate
.put("Date",new ExpectedAttributeValue(new AttributeValue().withS(date))
.withComparisonOperator(ComparisonOperator.LE));
return expectedAttributeSetupForConditionalUpdate;
}
This works fine for doing the conditional checking and success/pass when the hash+range key is already in the table, however if I supply a new range key, the conditional check seems to always fail.
The stack trace for the conditional check is not that useful to explain to me the problem but my assumption is that the conditional check is being applied even for brand new row creations and so it is failing.
Is there a way to get this working in one save operation or will I need to read first, check if exists, if yes then save without the conditional checks, if no save with the conditional checks ?
I was able to leverage Tawan's hint above and do something like this.
final Map expectedAttributeSetupForConditionalUpdate = new HashMap();
expectedAttributeSetupForConditionalUpdate
.put("name", new ExpectedAttributeValue().withExists(false));
expectedAttributeSetupForConditionalUpdate
.put("activity", new ExpectedAttributeValue().withExists(false));
expectedAttributeSetupForConditionalUpdate
.put("Date", new ExpectedAttributeValue(new AttributeValue().withS(date))
.withComparisonOperator(ComparisonOperator.LE));
final DynamoDBSaveExpression saveExpression = new DynamoDBSaveExpression() .withExpected(expectedAttributeSetupForConditionalUpdate)
.withConditionalOperator(ConditionalOperator.OR);
I wasn't able to use the newer Condition expressions since DynamoDB mapper doesn't support them yet in the version I'm using. Essentially this "passes" the conditional check when the row doesn't exist, but uses the date when it does exist.
I have a datatable with many columns, like so;
Name | Age | Foo | Bar | Etc..
Joe | 30 | foo | bar | Etc..
I need to now get this datatable into just two columns consisting of just the headers followed by their values, like so;
Header | Value
Name | Joe
Age | 30
Foo | foo
Etc... | etc..
This is so that a DataBinder can access it easily when the data is bound.
How can this be done, and do I need to do this at all?
EDIT: Including example code
asp.net
<div class="itemDetail col-s">
<div class="itemDetailLabel">
<%# DataBinder.Eval(Container.DataItem, "Caption")%>
</div>
<div class="itemDetailValue">
<%# If(DataBinder.Eval(Container.DataItem, "UIValue") Is Nothing OrElse String.IsNullOrEmpty(DataBinder.Eval(Container.DataItem, "UIValue").ToString()), " ", DataBinder.Eval(Container.DataItem, "UIValue")) %>
</div>
</div>
vb.net
Dim oldDataTable As DataTable = DataSource ''Which is a datatable of a single row
Dim newDataTable As New DataTable
newDataTable.Columns.Add("Caption")
newDataTable.Columns.Add("UIValue")
''Change the single row into multiple rows
fooControl.DataSource = newDataTable
fooControl.DataBind()
EDIT2: So for those that are still learning like me, this is called transposing. Thanks for #gofal3 for pointing it out
You have to transpose the DataTable. As far as I know there is no built in method, but you have to write your own code to do so.
But there are a lot of examples how other did it. eg: https://www.codeproject.com/Articles/44274/Transpose-a-DataTable-using-C or Transpose a datatable
I would to make the field descriptions and label texts in my pages multi-lingual. Originally they are in English and I could let the user translate them through Google Translate. In order to avoid translation errors I would like to implement a translation data model that contains
FieldDisplayName / LabelText
FieldDisplayName_DE
FieldDisplayName_FR
FieldDisplayName_IT
etc.
All the pages contain a page header fragment that contains a menu button, searchbox etc. like in the Starter App template. I am planning on integrating a dropdown widget in the page header that allows to choose between the languages (DE,EN,FR,IT,...). Is it possible to bind the display name to the user's selection? How would I have to implement that?
The easiest way (to implement/use/maintain) that would provide highest possible translation quality will be introducing Translation data model with the following structure:
+----+--------+------------+------------+------------+-----+
| Id | Locale | FirstName | LastName | Age | ... |
+----+--------+------------+------------+------------+-----+
| 1 | EN | First name | Last name | Age | ... |
+----+--------+------------+------------+------------+-----+
| 2 | RU | Имя | Фамилия | Возраст | ... |
+----+--------+------------+------------+------------+-----+
| 3 | DE | Voornaam | Achternaam | Leeftijd | ... |
+----+--------+------------+------------+------------+-----+
| 4 | ... | ... | .... | ... | ... |
+----+--------+------------+------------+------------+-----+
In this model every column represents unique label within your app and every row represents labels's translations for supported languages. This model can be easily used in label bindings:
#datasources.UserTranslations.item.FieldNameToTranslate
Maintaining these translation will be easy as well, just drag and drop editable table on UI.
Here is a query script for the UserTranslations datasource:
// Assuming that you already have robust user settings implementation.
var userSettings = getUserSettings_();
var query = app.models.Translation.newQuery();
query.filters.Locale._equals = userSettings.Locale;
return query.run();
Radically different implementation will be
Introducing Calculated Model with the same set of fields as in the previous approach
Using Model Metadata API to extract display names from the model's fields
Translate fields using Translate API
Populate calculated model record with translated values
Here is super high level server pseudo script for that flow:
var userLocale = getUserLocaleFromUserSettings();
var fieldsDisplayNames = getFieldsDisplayNames(app.models.Translation);
var translations = translate(fieldsDisplayNames, 'en', userLocale);
var record = app.models.Translation.newRecord();
mapRecordFieldsToTranslations(record, translations);
return [record];
After some trials a translation model turned out to be too laggy for my demands. Therefore I have hardcoded the binding expression into the labels I want to translate. The binding expression looks a little bit like this:
(#pages.UserSettings.LanguageDropdown.value == 'EN') ? 'Contact' : 'Kontakt'
I don't know if the follow code snippet intend to work in this way, because sometimes we "as developers" try automate creation of data display control where number of fields are uncontrolled and with similar data-binding, so before I review the application some guys left this :
Under ActiveReport_ReportStart() event :
for (Ind = 1; Ind <=CM.Length; Ind++) {
if (Ind == 1) {
Left = ((Line)rpt.Sections["PageHeader"].Controls["lnH8"]).Left + 0.05f;
} else if (Ind == 2) {
Left = ((Line)rpt.Sections["PageHeader"].Controls["lnH9"]).Left + 0.05f;
} else if (Ind == 3) {
Left = ((Line)rpt.Sections["PageHeader"].Controls["lnH10"]).Left + 0.05f;
}
TextBox TB = new TextBox();
TB.Size = ((Label)rpt.Sections["PageHeader"].Controls["tbColorway1"]).Size;
TB.Font = ((Label)rpt.Sections["PageHeader"].Controls["tbColorway1"]).Font;
TB.Width = ((Label)rpt.Sections["PageHeader"].Controls["tbColorway1"]).Width;
TB.Height = ((Label)rpt.Sections["PageHeader"].Controls["tbColorway1"]).Height;
TB.VerticalAlignment = VerticalTextAlignment.Top;
TB.Location = new System.Drawing.PointF(Left, ((Label)rpt.Sections["PageHeader"].Controls["tbColorway1"]).Top);
TB.DataField = "ColorText" + Ind + ColorwayNumber;
rpt.Sections["Detail"].Controls.Add(TB);
It doesn't have compilation error when is previewed, also others fields that are not auto-generated are displayed correctly (ReporHeader, ReportFooter), but IMHO I think is better to replace this mechanism by a subreport inside the detail section, of course these fields have to be displayed in Detail section of the report. Anyways I would like to see some recommendations because if is possible to auto-generated textbox or labels in runtime I will have to explain to boss why this code was not working, and if I have to use subreports instead, I need to know how to pass parameter (at least I need to work with two parameters for generate another sql query for it) and what "event" is proper to put script into it..
After I discovered that most important problem is to get report format changes by how many field/textbox were added to report detail in runtime restricted by a sqlquery return value, for example :
Returned SQLQuery value = 4
10 fields generated for detailed row 1
6 fields for row 2
4 fields for row 3
Detail fields are bound to a SQL Store Procedure*
Report will supossed to be printed/showed in this way :
//Report Init
Page 1 :
|field 1|field 2|field 3|field 4|
------------------------------------------------------
row1 | valA1 | valA2 | valA3 | valA4 |
------------------------------------------------------
row2 | valB1 | valB2 | valB3 | valB4 |
------------------------------------------------------
row3 | valC1 | valC2 | valC3 | valC4 |
------------------------------------------------------
Page 2 :
|field 1|field 2|field 3|field 4|
------------------------------------------------------
row1 | valA5 | valA6 | valA7 | valA8 |
------------------------------------------------------
row2 | valB5 | valB6 |
------------------------------------------------------
row3
------------------------------------------------------
Page 3 :
|field 1|field 2|field 3|field 4|
------------------------------------------------------
row1 | valA9 | valA10|
------------------------------------------------------
row2
------------------------------------------------------
row3
------------------------------------------------------
//End of Report
Any help will be appreciated
Thank you so much
It is perfectly fine to dynamically create fields on a report at runtime. The creation of those fields do indeed need to be done in the reportstart event or earlier (i.e. before calling ActiveReport.Run).
However, you could place the same logic to dynamically create those fields in a subreport and pass a parameter too, but in general subreports do impose additional overhead (and an additional query in most cases) so I wouldn't use a subreport unless there is a compelling benefit. However, there is a walkthrough on passing parameters to a subreport here.
The only thing that looks suspect in your code is the following line:
TB.Location = new System.Drawing.PointF(Left, ((Label)rpt.Sections["PageHeader"].Controls["tbColorway1"]).Top);
You are using the Top value from a control in the PageHeader, but TB is in the Detail section. I can understand reusing the Left value, but reusing the Top value wouldn't be consistent across different sections (Top is it's vertical position from the top of the section containing the control)
Now, it sounds like sometimes these fields do not appear on the report. Some things you can verify to troubleshoot the problem:
Determine if there is a binding problem or a visual/location problem. TO do this, just give the textbox a border or a background color or something so you can see it even if there is no text (due to failed data binding).
Start logging out the position of each textbox and the datafield value to a log file. When you notice the problem, go back to the log and see if you can identify what triggers the problem (maybe a specific index, location or datafield value?).
Finally, make sure that the page size (determined by the system's default printer) is not changing and maybe cutting off one of your dynamically added textboxes.
I was using Gridview for a while now and I have noticed that its very easy to create a simple table and populate it with date f.e.
ID Name Surename Phone .....
1 Tom Tomtom 111122233
2 Vic VicVic 21231231
3 Rik RikRik 123545343
So here we have a simple gridview with three records, every record is in one line!
What I need is to put one record info in three lines like here:
ID Name Surename Phone .....
/ 1 Tom Tomtom 111122233
record1 { Additional info: blablabla
\ More info: xxxxx
/ 2 Vic VicVic 21231231
record2 { Additional info: blablabla
\ More info: xxxxx
/ 3 Rik RikRik 123545343
record3 { Additional info: blablabla
\ More info: xxxxx
So here we have a Gridview and here we show One record's info in three lines...So how to do this?
I was using this code to populate my gridview when I have an Object of data but this works only with a single lines of records
private void grdMyGrid_RowDataBound(object sender, GridViewRowEventArgs e)
{
if (e.Row.RowType == DataControlRowType.DataRow)
{
MyObject ObjectEl = (MyObject)e.Row.DataItem;
e.Row.Cells[0].Text = ObjectEl.ID.ToString();
e.Row.Cells[1].Text = ObjectEl.Name.ToString();
e.Row.Cells[2].Text = ObjectEl.Surename.ToString();
LinkButton lbtConfigure = (LinkButton)e.Row.Cells[3].FindControl("lbtConfigure");
lbtConfigure.CommandArgument = Convert.ToString(ObjectEl.ID);
}
}
Templating rows like this is possible in a gridview, but the listview control is much better suited to this type of data.
Take a look here, this will get you started.
http://weblogs.asp.net/scottgu/archive/2007/08/10/the-asp-listview-control-part-1-building-a-product-listing-page-with-clean-css-ui.aspx
you can use templating for this purpose.
insert tables inside header template and item template(according to your need).
inside tables you can insert labels.
bind labels with the columns in your datatable.(Eval("columnname")).
now you got the gridview as you expected.