Working With Sharepoint 2010 Modals

By Author: Dylan Rodriguez
Total Articles: 131
Comment this article

At the time of SharePoint development each custom application is driven by some data either in one way or another. SharePoint development platform focuses on gearing of managing efficiently the flow of information so it's hard for SharePoint developers if they think to develop any solution without display of data or aggregation of data or sorting of data or filtering of data or creating or manipulating of data. With SharePoint 2010's inception there is huge demand for outsource SharePoint development as it includes more functionality than the older one providing SharePoint developers with new methods to work with both internal as well external data.

Example, If SharePoint developers want to create relationships between lists in SharePoint then in the similar manner they can create a foreign key relationship between database tables. Further they can query across these relationships for supporting the complex data aggregation in moderate way. There are new measures that can be used as they are designed for protecting the performance of data-driven SharePoint development solutions like throttling list queries for restricting ...
... number of items that are returned from query.

SharePoint developers can also interactively create external content types defining set of stereotyped operation on external services or databases. A data access method conforming to common and well recognized signature like creating, retrieving, updating and deleting of operations is a stereotyped operation. Creation of external lists can be done for effectively mapping the list into external content type which also enables users to interact smoothly with external data in the same manner as it is interacted with standard list data.

Also LINQ can be used to query SharePoint list data with the use of LINQ syntax which allows building of sophisticated queries including the use of joins. There is list of new features bringing with it many new design options and tradeoffs for SharePoint developers. See the 3 core approaches to define data models for SharePoint applications:

" Defining of a data model with the use of SharePoint data structures like lists and content types.
" Defining of a data model in an external data source like relational database, then creating set of external content types for exposing data to SharePoint through the BCS component. An alternate option is creating web service for wrapping the data source and creating your external content types from web service
" Creating a set of external content types for modelling and integrating an existing data source like WCF service, .Net type or a database for exposing the data to SharePoint through BCS.

At the time of working with custom SharePoint modals developers are allowed to collect the user data and then are allowed to close the modal. We will see now how developers can close modals once done. One thing that is important is that modals are part of context of entire page and JavaScript is used for either showing them or hiding them. There is a visual trick which superimposes the modal. There is an easy button of close/cancel for closing the modal DIV. Also there is an out of the box function for doing so. Developers just need to do in the page that renders in modal to assign OnClientClick event.

For More Information:- Sharepoint Development | Sharepoint Consulting