You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a way to set Baseline dates progrmatically using PSI or CSOM in Project online 365? I understand the below link says we cannot do it for Project 2013, but no such documentation is available for 365.
We were able to set the baseline using PSI by opening an instance of Winproj.exe and then calling PSI . We can still do it for 365, but just checking if there is a better way to handle it
The text was updated successfully, but these errors were encountered:
Hi sasankjonna, that article is still accurate for what cannot be done with PSI/CSOM in all versions, including Project Online. UserVoice would be a good place to let us know of key things that you would like to do - and be sure to include the scenario for doing it too. https://microsoftproject.uservoice.com/forums/914203-project-online
Best regards,
Brian.
@LunchWithaLens hi, is this still accurate? Why so? We want to set the baseline at a certain approval point in a project's lifecycle, after it has been planned sufficiently and budgeted sufficiently. We typically use the APIs and Project Online and PowerAutomate for everything. While we could do the same as the above contributor and use the PSI by opening an instance of Winproj.exe and then calling PSI, that seems like more of a hack and gap-filler to an otherwise robust web application and integration we're building. Thanks for your help.
Is there a way to set Baseline dates progrmatically using PSI or CSOM in Project online 365? I understand the below link says we cannot do it for Project 2013, but no such documentation is available for 365.
https://docs.microsoft.com/en-us/office/client-developer/project/what-the-psi-does-and-does-not-do#pj14_WhatPSIDoes_DoesNotDo
We were able to set the baseline using PSI by opening an instance of Winproj.exe and then calling PSI . We can still do it for 365, but just checking if there is a better way to handle it
The text was updated successfully, but these errors were encountered: