Project server: reserve keyword custom field odata feed

Issue: Odata error processing request:



We should not use reserve keyword while creating custom fields for project server (2010/2013/2016). What I faced while using Power BI through OData feed was facing conflict of my custom field with reserve keyword.
Cause: Duplicate custom field
There was a field called "Project ID" but this custom field internal name become "projectid" which is reserve internal field use by Project server for referencing different projects

Solution: 
Just rename custom field "Project ID" to "Internal Project ID" and it solve the issue.



 

Read More

Power Shell: Remove feature from SharePoint content database

During migration from Project server 2010 to Project server 2016, I faced missing feature error with Test-SPContentDatabase, so following script did the trick:

Remove-SPFeatureFromContentDB -ContentDB "ContentDBName" -FeatureId "FeatureID_GUID"

Read More

How to download deployed WSP from SharePoint central admin through PowerShell

This blog post is related to normal queries of SharePoint guys when they need to get deployed WSPs from SharePoint. I involved in migration of Project Server 2010 to Project Server 2016 so I need deployed WSP while testing mount database.

Following is simple script for downloading WSP through Power Shell:

 $Folder="C\EPMMigration"
foreach ($deployedSolution in Get-SPSolution)
{
         $id=$deployedSolution.SolutionID
         $title=$deployedSolution.Name
         $fileName=$deployedSolution.SolutionFile.Name
         $deployedSolution.SolutionFile.SaveAs("$Folder\$fileName")
}

Read More

View SQL table schema or definition

To view table schema definition one option is to right click table name view in design mode, other simple option is to view it through following query:

sp_help 'table_name'

It shows following:

• When table/object is created & its owner
• DDL of table (column name & its type & other definition details)
• Identity, indexes, contraint & foreign key this table/object is reference as

Read More

Temp path is too long while publishing website project

While publishing my asp.net mvc website I got following error:

Issue:

ASPNETCOMPILER(0,0): Error ASPRUNTIME: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. 5>

Solution:

For me following solution works:

• Go to web project folder e.g D:\Projects\SomeProject
• Then go to Properties\PublishProfiles folder.
• Open profile file in some editor i.e. profile_name.pubxml (not the file with *.pubxml.user)
• Add following under <PropertyGroup> tag
• <AspnetCompileMergeIntermediateOutputPath>c:\SomeShortTempPath\</AspnetCompileMergeIntermediateOutputPath> 
• Save file & publish it again, it works like charm
• Happy development

Read More