Saturday, November 19, 2011

Management of Master Lists in SharePoint with Choice Filter Lookup column


Almost every SharePoint project needs Lookup column. To create each lookup column we need to create separate list. If a requirement comes where developer needs to use master lists for different data then developer needs to create multiple lists which is resource consuming and maintaining multiple list also extra effort required for developer and administrator also. For this type of requirement I have created Choice Filter Lookup column. User can create one choice column in Master list and filter lookup column based on that choice column.


You can download the Source code from here

Current Scenario




MasterList1

MasterList2

MasterList3

MasterList4


MasterConsumerList New or Edit Form


MasterConsumerList View


Now above screen shot shows the real or actual implementation of requirements which generally SharePoint developers and Administrator follow for creating relationship of multiple caregory and reusability.If user want to add one more lookup column then user needs to create one more list for the lookup. The only problem is with above implementation is that it is creating multiple lists which increase the resource utilization and maintainbilty. Now I have tried to resolve the above implementation by creating Choice Lookup filter column. Please refer below screen shots for same implemetation with Choice Lookup filter
  ConsolidateMasterList and ConsolidateMasterListConsumer shows 2 new list for same implementation mentioned above

Consolidated Master List (with new column Category as Choice column with Values {Master1, Master2, Master3, Master4} for differentiate values or for filter values based on category)

Create Column of Choice Filter lookup column (Choose your filter category from the dropdown)




 List Settings view after adding 4 choice filter lookup column


Consolidated Consumer New or Edit Form

Consolidated Consumer List View 2MasterConsumerList View


Happy Coding !!!!!!!!!

1 comment:

Rakesh said...

Nice feature implementation :)