We are seeing odd things happen in MS project 2013.
Which Microsoft Project settings are you seeing being changed without user's knowledge?
It would be helpful to state if what version of CA PPM you're using and if you are using the legacy or the new driver
I'm not sure if below scenario is same as yours, but anyhow what we have seen and what is confirmed by CA is with:
This is a huge concern for us and now when Microsoft is moving to a 'ever-green' concept, we need a sustainable solution to be able to use MSP with PPM.
I voted on your idea:)
I agree. We are having so many issues with the new connector and 2013 SP1. I verified that some are due to the Microsoft updates, but there are so many, I can't tell which ones
We were told to ensure we do NOT have the Dec 2015 update, but DO have Feb 2015. The problem is that as patches are "bundled" you cannot tell if the original update is installed unless you try to install it again. Microsoft just released a Feb 9 patch to correct their issues with Dec 2015. It does not alleviate our issues, but it helped a tiny bit. In that case, yes, the code should not be constrained to specific updates. Thought I would pass that along, in case you needed to test that update .
The February 9 patch from Microsoft at least helped with our immediate problems, i.e. the connector is not stalling anymore and allocations are not being zeroed out.
Can you perhaps elaborate on what other issues you have? We are in the midst of upgrading from 13.3 to 14.3 and are now with the Feb 9 fixes able to restart the MSP-related test cases.
FYI I am having multiple issues with MSP 2013 (SP1) and the new driver on 14.3 . I am working with product development. My theory is that perhaps there are Microsoft patches that are killing us. But, regarding the Feb 9 patch from 2016: Be careful. Development has stated that though the patch seemed "helpful". it requires code changes on their end that they cannot implement until Armstrong. I was testing the 2013 new driver against 14.3 (non production) and baseline figures and work figures all changes in the TSV of MSP. There are several defects listed by CA that are they have fixed for 14.3 /14.4 based upon specific workflows. However, the development lead said they are only comfortable with the MSP Feb 2015 (yes 2015) patch to be supported with 14.3. Beyond that, they feel Microsoft caused too many issues. This kills us as we push out updates almost as soon a they come. Anyway...
If your workflow is simple. you may not run into any issues, but still I wanted to pass that on!
Ok, thx for the update, we actually have quite complex test cases that should catch all issues, let's see what we find.
We've also been in touch with product development with more or less heated discussions about what 'cannot' be implemented between versions according to CA's 'patch policy'. From technical point of view I understand how and partly why the policy is as it is. From customer point of view we see it like this: if something is severely broken it needs to be fixed quickly and not after 1-2 years with next Clarity version. We also don't care who needs to fix it (CA, Microsoft or other parties) as it is out of our control.
agree.. it is frustrating when they cannot patch the connector. It is always the "next release". Our major defects still appear in 14.3 with the new connector. This causes two problems: We cannot get off of 2010 (way out of compliance) and puts us out of compliance with the Microsoft 365 standards of "cannot mix versions". We are already looking to 2016 within the next year, so I can only imagine what will happen there.
The connector code somehow needs to be "adjusted" so that it is not so dependent upon a patch. I was floored when I heard the dev tem will only support a year backwards??? that is not a good reflection of keeping up with technology. The problem I have is that there are MSP updates and then Microsoft pushes out Office , Skpe and visio updates that all shows under Project 2013 updates in the installed updates. I have no idea which one(s) are impactful, but I am starting with the MSP only.
Keep us updated on what you find. For us, we use Fixed work tasks, the users enter work hours (i.e. ETC) in the TSV of Microsoft project for each month (or weeks). Baseline it in MSP. Save to PPM. Close MSP. Re-open the project.
On the Feb 2015 patch only, I was able to get one project to have the numbers stick. But, once I got out to the year end or skipped months (our defect that was fixed in 14.2 patch 5), the forecasted monthly numbers an baseline are all nuts (wrong months., or changed to decimals). Some are "normal" .. it is a hodgepodge of mess depending on what we enter.
Once the updates were pushed out to the test server, then the one project that was working now has the baseline figures all wrong and some of the work figures are all wrong (ex: 10 changed to 9.88 or 15 changed to 14.98, etc).
In our production environment we are still on MSP2007, obviously with the legacy driver. We are recommending our users to use Fixed duration tasks, but apart from these two things we are in more or less identical situation as you. We are also eager to go to Office365, but even with next Clarity version 'Armstrong', CA is not going to support the MSP-version being part of the cloud service (i.e. MS Professional Pro). This is at least not our definition of being 'agile'.
CA promised to publish a KB-article within the upcoming days related to their official test results of MS-patches after Feb. 2015. We'll wait with our own testing until then. If there are still severe issues that won't be fixed, this might be the final nail in the MSP-integration coffin for us...
I did a lot of documentation a few years ago on MSP and Clarity and even proved some defects in MSP itself that were being blamed on Clarity. Microsoft as of MSP 2010 finally added some features that were able to resolve some of the long standing MSP <-> Clarity complaints. But others exist.
MSP, does some really cool things and when you muck about with some of the fields (columns) it can create some unpredictable results with Clarity. What I have recommended in the past is once you have a version of MSP that is working well with Clarity, stick with it, and only apply patches if necessary and supported by Clarity (otherwise something may break). I also recommend a SOP on how the users are to use MSP with Clarity and what parts of MSP not to touch, what data is updated in MSP and what is updated in Clarity. This is necessary to ensure issues are kept to a minimum and to ease the support burden.
Whiule I have been away from MSP and Clarity for the past year and a half, I am jumping in both feet again as I see my currenlt employer moving to this direction in the next 8-12 months and will need to have SOP's created for this.
I will post what I find in the community.
I realize this thread is a year old, but we are currently trying to upgrade MSP 2010 to MSP 2013 while on v14.2. This is prep work for upgrading to 15.2 over the summer, since 15.2 does not work with 2010. Would you be able to share your documentation? firstname.lastname@example.org
Retrieving data ...