Forum Discussion

FabioBrandao's avatar
FabioBrandao
Copper Contributor
May 17, 2019

Add a Enterprise Resource to project with CSOM on PowerShell

I'm using PowerShell with CSOM to add an enterprise resource to a project on Project Server 2016 (on premisse).  I found some examples with C# that guide me, but it's doesn't looks like a common thi...
Ade_Budiman_Lim's avatar
Ade_Budiman_Lim
Brass Contributor
Oct 09, 2020

FabioBrandao Sometimes it's different way between Project Online and Project Server. I think your code is for Project Online and not for Project Server. Have you try by using this reference?
https://vamsi-sharepointhandbook.blogspot.com/2016/06/project-server-2013-build-project-team.html

FabioBrandao's avatar
FabioBrandao
Copper Contributor
Oct 09, 2020

Ade_Budiman_Lim no, it's on an On Premisse environment. And it is an unaccepted bug from Project Server CSON on PowerShell. I made a mistake talking about my goal to support of Microsoft, and after that they sad repeatedly "It will not work" referring to my goal, and not accepting the point I exposed on this post. I'm very frustrated every time I report things like that and they sidetracking me (this case took around 5 month to at the end I say "you will not focus on my problem and don't stop saying 'it will not work', close this case please.")

It is a bug, period. But they can't see it.
The solution was go to C#. There, exactly the same logic (creation of objects, callings and attributions) and it worked very well.


PS: Today I don't know if it was fixed on PowerShell.

Resources