Geek Answers Handbook

List of the Best SharePoint Lists

I am building an application using a SharePoint list to store data. The data design would be very similar, as if you put it in a relational database, with elements such as many or many relationships, primary keys, foreign keys.

I would like to know what are the best practices?

There are a few questions that I have in mind when creating a list:

  • SharePoint itself contains a hidden identifier. Should I create my own id?
  • What is the best way to reflect a foreign key? Is this just creating a search field? or you think it's best to create one line text, and then my program will link the identifier. Which one to use?

Any other tips on this would be helpful. By the way, I'm using SharePoint 2010.

+5
source share
5 answers

I would not do that. If it will work as a relational database, you should simply use a relational database. The problem you encounter with foreign keys is just the tip of the iceberg when it comes to using lists as database tables.

+6
source

I won’t go there either. Especially not through the BDC. If you need to integrate with relational data, you can also do this directly from your .NET workflow code. You can still use SharePoint to start workflows and maintain task lists, etc.

, . .

0

. , .

SharePoint 2010, . BDC BCS SharePoint. : a. b. BCS.

a) , - . b) , BCS . , . . , - , "". , , ...

0

, SharePoint . , , SharePoint, SharePoint .

Channel 9

http://channel9.msdn.com/Learn/Courses/Office2010/AccessUnit

0

In some cases, you would like to save your data in a database, not in SharePoint lists, if you are sure that this is exactly what you want to do, then you create your database and tables as usual, and then create a list with using the type of external content that you define in SharePoint to reflect your data in your database.

Additional information on the topic here: http://msdn.microsoft.com/en-us/library/ee557243.aspx

0
source

More articles:


All Articles