Within .Net 3.5 SP1 and higher, if I do the following:create a database with many FK relationships, drag-and-drop create a LINQ class, create a page with a LINQDataSource & simple ASP.Net GridView, I can then add some simple field tags like:
and presto! I have a grid that shows the relational data, not just ID integers.
I have not yet found a way to access this power using either of the Infragistics grids. The behavior I've experienced so far is that it seems that I am limited to the equivelant of the ASP.Net GridView's BoundField, even when the data source for the Infragistics grid is a LINQDataSource which is pulling from the DataContect model/class.
Is it true that from the Infragistics grids that I do not have access to this Dynamic Data? Would code-behind be required to make it available to the Infragistics grids? Am I mistaken?
Any ideas or suggestions would be appreciated.
-Gary
Dinesh,
Thank you very much for the time you have given to this issue, and for submitting it to development!
,Gary
Hi Gary,
After some research, this issue has been determined to be a new feature request. I have sent your feature request directly to our product management team. Our product team chooses new feature requests for development based on popular feedback from our customer base. Infragistics continues to monitor application development for all of our products, so as trends appear in requested features, we can plan accordingly.
We value your input, and our philosophy is to enhance our toolset based on customer feedback. If your feature is chosen for development, you will be notified at that time. Your reference number for this feature request is FR12444.
If you would like to follow up on your feature request at a later point, you may contact Developer Support management via email. Please include the reference number of your feature request in the subject and body of your email message. You can reach Developer Support management through the following email address: dsmanager@infragistics.com
Thank you for your request.
Showing DynamicFields as columns is only half of the magic of DynamicData.The other half is being able to use DynamicFields within field templates. As of today, If I were to attempt to migrate as much as possible from basic framework controls to Infragistics controls, the controls I would need to be DynamicData-capable would be:
WebDataGridWebHierarchicalDataGridWebTextEditorWebDataMenuWebDataTreeWebDropDownWebImageViewerWebHierarchicalDataSourceWebGaugeWebChart
To date, due to some foreign key limitations of the v1.0 Entity framework, I'd primarilly been levereging DD using LINQ models. I hope, now that a more mature EF is available, I will be leveraging both LINQ & EF.
Thanks for the update. Do you need it for all the Infragistics grids including the WebGrid and WebHierarchicalDataGrid ? Just wanted to be clear on this so that I pass on the correct information across. Thanks.
Dinesh,Thank you very much for your response!I use DynamicData, levereging Entity Framework and LINQ DataContext models heavily in my work.(I would impliment use of this feature immediately, upon being available in the Infragistics WebGrid!)The fact that I'll need to stick with the default GridView that comes with the .Net framework for now is disappointing, so anything I can do to help Infragistics update their controls... just let me know!