We're trying to create ProjectWise 365 projects using PowerShell, but we're encountering some issues trying to get it to work. I've more or less copied the example given in the help dialog for the Add-PW365Project command--script shown below:
Upon attempting to run this script, we're encountering some errors. We're getting either a "object reference not set to an instance of an object" error, or a "unrecognized Guid format" error:
What's odd is that the (rich) project does get created and can be seen in ProjectWise Explorer...
And it can also be seen in our ProjectWise 365 portal...
However, upon trying to open the project in the portal, we're getting this message:
And then when we click on the link, we get this:
So now we have these projects that are currently "stuck" in our portal which are displayed, but are not provisioned--and as such, we can't get rid of them. The only thing we can think of that might be causing the error is the $pw365id variable in the script not having the proper guid format. The example given in the help for the Open-PW365Project command shows the following:
We think that the $pw365id variable is not returning the correct guid format. If there's a way to get the guid of the ProjectWise 365 project, perhaps that might help us out.
Sorry that I didn't see this earlier. I have seen similar problems when creating and associating PW365 projects. The web team has not been able to identify the underlying issues, so, in the meantime, I am going to remove the association logic from Add-PW365Project. The cmdlet should still create a PW365 project, but I've seen some anomalies on PW365 project creation both through the API (PowerShell) and the portal. I'll make a comment about in the next release log.
BTW, I have better results creating PW365 projects when using a non-federated IMS identity. I don't know if this is just my account or if there is something systemic. If you can setup a non-federated account in your IMS org, it might be worth a try.