Tag Info

Hot answers tagged

2

While not exactly like your accounting structure, you could name them P01, P02, etc and it will sort as you'd expect.


2

Select the option for "Return field as" to Lookup Value, while selecting [%Current Item:Application%] For reference, have a look at screenshot below.Instead of "As String", select Lookup Values,Comma Delimited


2

Via Central Administration: Manage web applications / Select the web application, then from the drop down list 'General Settings' select 'Resource Throttling' / change the value of 'List View Lookup Threshold' Or via PowerShell: $wa = Get-SPWebApplication http://YourSharePointSite $wa.MaxQueryLookupFields = 20 $wa.Update()


2

Instead of PSI I suggest you to work with the managed object model of Project Server. That is much more developer friendly. Last year I wrote a post about how can you list lookup table entries: using (var projectContext = new ProjectContext(pwaUrl)) { projectContext.Load(projectContext.LookupTables, lts => lts.Include( lt ...


1

That is the limitation with importing a spreadsheet. You could make them choice columns or lookup columns to other Sharepoint lists you'd need to create. Once created, you'd then need to update the data, datasheet view could help speed that up, or you could then try deleting all the content and pasting the Excel data into datasheet view.



Only top voted, non community-wiki answers of a minimum length are eligible