Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, Power Apps, Power Automate, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
Got this error message when trying to connect MS project to PSA
I'm using a demo environment with PSA version 220.127.116.11 on a production instance.
I've installed the add-in from this URL:, which is V2 but it can't find another one. https://www.microsoft.com/en-us/download/details.aspx?id=54299
Sorry for any confusion this may have caused our dearest customers.
Due to differences between the Potassium and Calcium versions of PSA there is need to have 2 versions of the Add-in.
For PSA v3.4+ (Calcium), use this www.microsoft.com/.../details.aspx. Note that this Add-in is not supported in PSA versions 3.0.-3.3
For PSA v2.x(Potassium) use this www.microsoft.com/.../details.aspx
Thank you Chinua, it fixed my issue!
I highly suggest that you update the documentation on docs.microsoft.com and the redirection link when clicking on the MS project button on a project. The documentation is really misleading.
Anyway thanks for the help!!
I'm trouble shooting the same thing; however I'm not receiving the error and on version 2.4. Others on the team need to have the admin role in d365 to by pass this issue. Is Visual Studio required in addition to the add-in?
Business Applications communities