Xperienzz https://docs.microsoft.com/archive/blogs/souravnayyar/feed.xml sharing 'experiences' Wed, 17 Apr 2019 03:50:33 GMT en-US hourly 1 Getting selected columns from a sharepoint list using SPQuery.ViewFields https://docs.microsoft.com/archive/blogs/souravnayyar/getting-selected-columns-from-a-sharepoint-list-using-spquery-viewfields Sun, 05 Aug 2007 04:11:00 GMT https://blogs.msdn.microsoft.com/souravnayyar/2007/08/05/getting-selected-columns-from-a-sharepoint-list-using-spquery-viewfields/  

Sometimes there is a need to query data pertaining to only specified columns from a sharepoint list.

Let's say I have a list "Employee" with columns - Name, ID,  Age, Sex, Address, SSN etc. and I just want to retrieve data corresponding to columns Name & SSN for Employee with ID = 9.

Syntactically, it can be accomplished as below -

// Code starts here

SPListItemCollection itemCol = null;

SPSite site = new SPSite("site url");
SPWeb web = site.OpenWeb();

SPList objList = web.Lists["listName"];
SPQuery qry = new SPQuery();
qry.Query = "<Where><Eq><FieldRef Name='ID' /><Value Type='Text'>"9"</Value></Eq></Where>";
qry.ViewFields = <FieldRef Name='Name'/><FieldRef Name='SSN'/>

itemCol = objList.GetItems(qry);

// Code ends here

 

  

]]> Compatibility meter - Share point 2007 and MS Access 2007 https://docs.microsoft.com/archive/blogs/souravnayyar/compatibility-meter-share-point-2007-and-ms-access-2007 Sun, 10 Jun 2007 08:37:00 GMT https://blogs.msdn.microsoft.com/souravnayyar/2007/06/10/compatibility-meter-share-point-2007-and-ms-access-2007/ I was on this engagement where I had to make use of management information stored in MS Access 2007 and MS Excel 2007 in a share point 2007 site. 

It’s been 150 years since I used Access to do some basic database management stuff in a small library management application and here was with some data in access, some in excel and a share point site.

If it was not for the OOTB features of Access 2007 for integration with share point 2007, the same set of tasks would have taken ages or lots of custom coding but I didn’t have to do anything other than some cool OOTB features of Access 2007 to actually make things work.

Some of these features are –

Linked tables – This is a nice feature and has been with Access since quite a long time now. Linked tables allow Access to have a table directly linked to a share point site. This allows updating  the sharepoint list by just updating the Access table. This helps user who are comfortable using Access to just use it and in turn update the corresponding share point lists.

Appeding data from an excel file to a sharepoint list - The OOTB excel import feature of sharepoint allows to create a new list on the basis of an excel file but there Is no OOTB feature to append rows of data from excel to a share point list.

Access 2007 comes to help here. An excel file can be imported into an Access 2007 table. This feature allows to create a new Access 2007 table based on an excel file and also allows to append rows from an excel file to an Access table.

If you read the paragraph above and replace "table" with a "linked table", you have got a way to append excel rows to a share point list. Interesting huhhhh J.

Similarly there are many features in Access 2007 that allows it to integrate with sharepoint 2007. Look closely, you might be able to implement lots of your requirements using these OOTB features.

 

]]> Establishing relationship between two lists on a share point site https://docs.microsoft.com/archive/blogs/souravnayyar/establishing-relationship-between-two-lists-on-a-share-point-site Sun, 10 Jun 2007 07:26:00 GMT https://blogs.msdn.microsoft.com/souravnayyar/2007/06/10/establishing-relationship-between-two-lists-on-a-share-point-site/ Before I got to know about what I am going to write here, I was pretty convinced that there is no way to establish a relationship between two lists using lookup columns in case of the source column having multiple copies of data.

Using OOTB features of share point a user can only associate a single field from source list with the destination list in form of a lookup column. It should not be the ID since ID won’t be user readable and if it is only a title then it definitely fails in case of multiple copies of title with same value.

 

Just to make things a bit more clear –

If in case we have two lists – Account, Contract. An Account can have multiple contracts. In order to establish a relationship between the two, I associated column – Title from Account list with column Account Name from the Contract list using the look-up column type.


This relation-ship works well as long as the title column in Account list is unique. But to use this relationship in share point filters, connections etc. we need to have unique instances of title column to make it work accurately.

Situation can be handled accurately if CAML and values returned by a look column are put to use while doing some customization.

List of items returned by the CAML query contains values in the form ‘FieldID;#FieldName’ for lookup columns, Where FieldID and FieldName corresponds to the ID and title columns values respectively for the source list.

Using the above form, the items can be searched for the corresponding ID’s. This property can be put to good use in scenarios such as  - populating values in a dropdown on selection change of another drop down list.

 

]]> Test Page https://docs.microsoft.com/archive/blogs/souravnayyar/test-page Mon, 02 Apr 2007 06:38:00 GMT https://blogs.msdn.microsoft.com/souravnayyar/2007/04/02/test-page/