Timeline for SP2013: Site columns: lookup to custom list, or select list?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 10, 2016 at 17:04 | comment | added | Evariste | In all cases, have in mind following "limits" in SharePoint: 1. no more than 5000 items per view (see for instance sharepoint.stackexchange.com/a/163427/35604); 2. no more than 8 lookup fields by list. If you're below these limits, you should not notice any performance problem at all. Even when above, there's a lot of chances you're still OK (but for the 5000 items, you'd have to configure the list so it can handle it). | |
| Feb 10, 2016 at 16:33 | comment | added | Alexx | Thank you for this very detailed explanation! I assumed the lookup field would be the easier way to go (making assumptions about the underlying database implementation). My biggest concern is, if there are a significant number of these types of lookups (versus just plain drop down lists), how does that overhead affect the performance... but at this point I don't really concern myself overly with it, as we are the first site on the new 2013. :) Thank you! | |
| Feb 10, 2016 at 16:31 | vote | accept | Alexx | ||
| Feb 10, 2016 at 16:30 | vote | accept | Alexx | ||
| Feb 10, 2016 at 16:30 | |||||
| Feb 10, 2016 at 15:56 | history | answered | Evariste | CC BY-SA 3.0 |