Two Activity Code Types in P6 Database
Are there known bugs if you have a global-level activity code defined and also the same code definition existing as a project- or EPS- level code? This can be caused by importing from aan outside database (client, subcontractor, etc.), for example. This happened to me in the past, but I thought I cleaned up the code definitions (but I am 58, so...).
I'm running P6 Pro v8.3.3 in a hosted environment. Any information you can provide would be appreciated.