Just downloaded and installed latest 2014.1 Service Release (IgniteUI_20141.2249_SR)
When running my application I now get the following error when trying to open a page with the igGrid on it.
Please assist.
Hello Mark,
The RowTemplate option has been deprecated in 2014.1. To get your templating to work in this version you need to split it into column templates and add those to your columns definition.
I hope this helps! Please, let me know if you have any other questions and/or concerns!
Best regards,
Stamen Stoychev
Stamen
As I am new to Infragistics, please advise how this should be changed:-
<div> @(Html.Infragistics().Grid(Model.Rows.AsQueryable()) .ID("vmLoanList") .Width("100%") .Caption("Loan List") .AutoGenerateColumns(false) .RowTemplate("<td>${Id}</td><td class='rightAlign'>${AccountNo}</td><td>${GoodsDescription}</td>" + "<td>${AgreementType}</td><td>${Status}</td><td class='rightAlign'>${Balance}</td><td class='rightAlign'>${Arrears}</td>" + "<td class='centerAlign'>${NextInstDate}</td><td class='rightAlign'>${NextInstAmount}</td>") .Columns(columns => { columns.For(x => x.Id).DataType("string").Hidden(true); columns.For(x => x.AccountNo).DataType("int").Width("40px"); columns.For(x => x.GoodsDescription).DataType("string"); columns.For(x => x.AgreementType).DataType("string").Width("150px"); columns.For(x => x.Status).DataType("string").Width("110px"); columns.For(x => x.Balance).DataType("number").Width("110px").Format("0.00"); columns.For(x => x.Arrears).DataType("number").Width("110px").Format("0.00"); columns.For(x => x.NextInstDate).DataType("date").Width("100px").Format("yyyy-MM-dd"); columns.For(x => x.NextInstAmount).DataType("number").Width("110px").Format("0.00"); }) .DataBind() .Render() ) </div>
Many thanks
Hey Mark,
Did you have the chance to put up a sample?
Hi Boris
Please follow this link to Mike P in developer support.
https://ko.infragistics.com/my-account/support-case/CAS-132577-C6Y4F2
I would appreciate urgent attention on this issue.
I downloaded the sample project attached in this case (CAS-132577-C6Y4F2) and tested it on my side. However I couldn't see any inappropriate behavior of the grid related to the column templates. Could you point me to the right direction about what should be the current issue in this project and how it should be reproduced (steps to reproduce it)? Looking forward to your response.
Sincerely,
Tsanna
Attached is a pdf document with screen shots depicting the Template problem as well as the IE/Chrome problem with the igGrid Caption issue that was supposedly sorted out in 2014.1 Service Release.
Please revert back to me urgently.
While I couldn't quite reproduce the grid's state from the screenshots you sent with your sample I did notice some column misalignment which is caused by referencing bootstrap.css. It contains some global table rules that conflict with igGrid's layout when the width is set in pixels. To fix those you'll have to enable the Responsive feature. Enabling it may also resolve the much more severe rendering issues you show with the screenshots.
To enable the Responsive feature you need to add the following line to your Features definition:
.Features(features => { ... features.Responsive(); })
I hope this helps!
I created a support case on your behalf with number CAS-140841-G5F2C8 and will continue to update you through it.
You can find your active cases under Account - Support Activity in our website.
Morning Stamen
I will update the sample application and will send it to you as soon as possible.
You said that you were not experiencing the problem with my sample, so would it be possible to zip the complete solution including the bin and references folder and email it to me so I may work through them both to see if I am doing something wrong when bringing in the new 2014.1
Please advise
I am just checking to see if you were able to update your sample. Are you still experiencing issues with the column templates?
I am looking forward to hearing from you!
I am looking forward to the updated sample! Please make sure you are seeing what's shown on the screenshots you sent earlier when running it with the latest version. Unfortunately, your previous sample seemed to work properly here making identifying the problem a lot harder.
I'll make sure to dig into it immediately after you post it.
This had no effect on the problem.
I will update my sample solution with your proposal and will forwrd for your comments.
This is having a severe impact on our development and needs to be resolved as soon as possible.