User Profile & Activity

leo Chandra Member
Page
of 14

Hi Cristobal,

Please make sure the bindingProvider's targetViewName and the view's identifier in CustomCell match.

For a sample, you could see DataDrawer sample that will show you an example of UITableView with Custom Cell Template on Drawer. For a walkthrough about how to use custom cell template for iOS UITableView, you could refer to Create Custom Cell Template for iOS UITableView.

Best Regards,
Leo

Posted: May 12, 2015 7:07 AM

Hi Agus,

Please check whether you have the following reference on you WebAPI project:

  1. EntityFramework
  2. Intersoft.Crosslight
  3. Intersoft.Crosslight.Data
  4. Intersoft.Data.WebApi
  5. System.Web.Http.OData
  6. Microsoft.Data.OData
Please also make sure that your WebAPI project also have reference to DomainModel project. After that, please try to run Model.Controller.tt custom tool and rebuild DomainModel project. If there is no problem with the DomainModel, you could proceed with clean and rebuild your WebApi project. Hope this will be usefull.

Best Regards,
Leo

Hi Alexandre,

We cannot let the WebGrid hit directly the database in this case.

For your information, WebGrid won't directly hit the database. After all the one that will handle all operation with database would be the datasource that has been used.

I would like to confirm whether there really a need to display all 90 000 rows at once? After all, displaying such a large amount of data was not a good approach. The data should be chunk and feed it to webgrid which would be display to user. We typically suggest the developers to load data in server-side paged mode which is the best practice.

For your information, WebGrid actually used standard data API from .NET, which is DataSet. And most operations are done through DataView. However, of course, if the data is not paged from server, then it'll be a lot in the web server. If you want to process the data in web server, you should try to process the data then feed the final result to WebGrid (after the data was paged).

Best Regards,
Leo

Hi Alexandre,

For your information, WebGrid has paging feature that could be used to handle a large mount of data. Enabling pagging will significantly boost your performance as user won't required to see all 90.000 data at once and server should only served the required data on the time user need it. So I suggest you to enable WebGrid's paging feature, either Classic Pagging or Virtual Load. And as addition, you use the ISLinqDataSource as the WebGrid data source to get the maximum performance on server side. I hope this will help you.

Best Regards,
Leo
Posted: May 7, 2015 6:02 AM

Hi James,

I have test your sample and this issue only happen when viewed on IE browser. For your information, this issue has been fixed on WebGrid 9 so I suggest you to update your WebGrid.

Best Regards,
Leo

Posted: May 6, 2015 6:34 AM

Hi James,

I have test this by adding a WebCombo and a TextBox to Enterprise.aspx WebGrid sample. Unfortunately, I could not reproduce your issue. I could select/focus on the TextBox and WebCombo that has been added. For your information, the test was conduct on IE 11.

I am willing to advise you further but in order to do so I would need you to provide me with a simple sample that I can use to observe the problematic behaviour.

Best Regards,
Leo

Hi Mahesh,

You could change webgrid page size before data was loaded on export action. And after that, change back webgrid page size after export was done. For your reference, I have attach a simple sample. Please have it evaluated on your end by adding it to WebGrid default sample.

Best Regards,
Leo

Posted: May 4, 2015 10:17 AM

Hi John,

"Multiple Control With the same ID" error message usually occur when you dynamically add cached user controls to an Webform. Please try check if you have dynamically add a control with webgrid1_h id in the CodeFile.

Best Regards,
Leo

Hi Jimmy,

Our developer team has add the support for this feature and it will be available in our next release.

Best Regards,
Leo

Posted: April 29, 2015 10:18 AM

Hi James,

I am sorry to inform you that the fix for 'ASPNET-157' will be delayed. I wil give you an update on any news I heard about 'ASPNET-157'.

Best Regards,
Leo

All times are GMT -5. The time now is 1:45 AM.
Previous Next