hi emad,

please let’s know how you did it?

hi muhammad,
i’m sorry you’re having trouble. to my knowledge, p6 doesn’t support persian and that’s probably why you’re having difficulties.

hi a.j.
p6 supports japanese language. it might be the case where you will also have to set p6 to be in japanese.

if using p6 v8.0 and later, in the prmbootstrap.xml file, located %userprofile%\application data\oracle\primavera p6\ under the following section:

the language currently being used for the project management client application is stored: in the following registry key, unique to each user who logs into a workstation:

if using p6 v6.x – v7.0, in the following registry key unique to each user who logs into a workstation: hkey_current_user\software\primavera\6.0\shared\international
if using p6 v8.0 and later, in the prmbootstrap.xml file, located %userprofile%\application data\oracle\primavera p6\ in the beginning of the internationalizationsettings element:

any ideas for what i might be doing wrong?

thank you,
a.j. wolnski

thank you luis.

emad, what process did you follow to do this?

better yet, keep the original field unchanged and import the translation (or any alternative/ extended description) in a separate (user defined) text field (to be optionally displayed, possibly inaccurate pending a manual check, possibly longer than the standard field max length, containing unrecognised characters etc)

wbs names (which is project specific data, but cross-referenced in database tables that span your eps tree, project, as wbs root, down to the lowest level of wbs) as well as most hierarchical global data structures (e.g. obs, res/ role bs, cost accnts, global/ eps/ project specific activity codes etc) can, or at least could, in 32-bit previous p6 versions, be modified using sdk (software development kit) and the some dedicated (macro-enabled) excel files.

nevertheless, wherever possible, consider using user defined fields (udf’s) created for the relevant entity (project, wbs, activity, resource, resource assignment, expense) in order to add (via regular excel export-import, global changes or sdk) any such alternative descriptions or extended narratives (e.g. for translations or extended text descriptions of up to 255 characters, as opposed to normally 20 for id’s and codes and approx. 120 for names and descriptions).

the advantages of using udf’s alongside the standard p6 fields is two-fold: trace-ability (as stated above) and safety. udf values (in this case text) can be edited (populated, modified) without restrictions, cleared (blank values) or even deleted (the udf itself) with little risk of overwriting, losing or corrupting project/ database data

regards,
tibi

unfortunately, wbs descriptions and activity code descriptions can’t be updated via excel in p6. i don’t have a solution for this, so for now, it’s a manual effort.

it might be related to your versions of excel. read about 64-bit vs 32-bit in this post.

ed, great suggestion!

can you let let me know why i cannot import/export (via p6 16.1) using 64 bit. i followed the oracle knowledge base instructions to load access database redistribution and set to /passive.

thanks.