Issues Resolved by SP4 [return to top]

Activity Details Tabs

· prim41103: Changes are not committed to database when using Up and Down arrows in activity details.
After making changes to Activity Details, they are not committed to the PM database when using the Up or Down arrow keys to move to another activity.

Baselines

· prim20369: Baseline data for activities does not display after changing Activity IDs and inserting new activities in the current project.
After creating a baseline for a project, if you change activity IDs in the project and add new activities (that are not in the baseline) to the project, baseline data does not appear for the changed activities.

· prim40252: Cannot edit EPS activity code values in the columns for a restored baseline project.
There are several issues related to editing baseline projects:

- You cannot edit EPS activity code values in the columns of a restored baseline project.

- When opening and project and a restored baseline project, you can edit only the EPS activity code values in the column of the current project.

- When opening a restored baseline project, the EPS activity code values appear only in the Codes tab of the Activity Details form.

Calendar Display

· prim31119: Why are weekends not shaded in the Gantt Chart Week/Day timescales, as they were in previous versions of Project Management?
With the default global calendar set to a typical 5-day workweek, Saturdays and Sundays (which are listed as non-work days) are not shaded.

Copy/Paste

· prim47454: When copying/pasting projects with interproject relationships, if the option “Only between copied activities” is not selected, it then creates external relationships between the old projects and the new projects in Project Management 5.0 service pack 3.
When grouped by EPS, external relationships between projects are created even if the relationship setting for copying and pasting projects is not “only between copied activities.”

· prim47517: Copy and paste project setting for relationships “only between copied activities” does not create interproject relationships in 5.0 SP3
When grouped by EPS, relationships between projects are not created if the relationship setting for copying and pasting projects is “only between copied activities.”

Enterprise Project Structure Dialog Box

· prim51087: With 5.0 SP3, the Enterprise Project Structure menu lists column headings as Project ID and Project name instead of EPS ID and EPS Name.
On the Enterprise Project Structure dialog box, the column headings “EPS Project ID” and “EPS Name” are mislabeled as “Project ID” and “Project Name”.

Gantt Chart

· prim13671: Relationship Lines not being drawn when using filter.
When a filter is applied to activities, relationship lines are not added, for example, when new activities that include relationships are added.

· prim19957: Bar changes position when row height is increased to 40 and above.
Bars in the Gantt chart do not align properly if row height is 40 or above.; also, the baseline bar might disappear or display in the wrong place.

Layouts

· prim34395: Intermittent AVAA0 errors when changing layouts in Primavera Project Management 5.0.
When changing layouts in the Project Management module, intermittent AVAA0 (access violation) errors occur.

Login Dialog Box

· prim23218: Fields are cut-off or missing from Project Management, Methodology Management, and Portfolio Analysis.
Unable to enter password on the Login screen because the Password field is either missing or shrunken.

MPP Import/Export

· prim46599: FPDBZ-3853-D error when trying to import Microsoft Project files into Project Management 5.0 SP3.
After installing Primavera 5.0 SP3, cannot import MPP files for Engineering and Construction.

Printing

· prim29901: Event code: GPTWI-2179-9 when printing from Print Preview or File, Print.
When printing from Print Preview or File/Print, the error GPTWI-2179-9 (Invalid window for printing) is displayed if a Gantt chart is one of the items being printed.

· prim46479: Print Preview in 5.0 Service Pack 3 does not show the Gantt Chart when selecting lowercase timescale dates.
Entering lowercase alpha characters in Timescale fields causes the Gantt chart to not display.

Project Architect

· prim48843: Error: “CCF”C-xxxx-x/Cannot create file “C:\JMc5857Log.txt”. Access is denied. (When creating a project using Project Architect.)
When creating a project with Project Architect, the message above is displayed.

Reports

· prim28743: Page setup options are not saved when Report Wizard report is saved.
Page setup options, including custom headers and footers, are not saved when the Report Wizard report is saved.

· prim50043: Multiple Byte – report function unable to insert line break for Asian Character.
Information is missing in reports because there is no word wrap or automatic line feed for Asian characters.

· 20023711926: Grand totals are not correct on a grouped by resource report.
When grouping by resources, the grand totals in reports are not correct.

Resources

· prim42323: Resource information changes when making change to resource assignment.
After applying a global change, if you replace a resource assignment by editing the Resource Names on the Resources tab, the resource name of the newly assigned resource is overwritten in the resource dictionary by the resource name of the resource that was originally assigned to the activity.

Scheduling

· prim43847: Recalculate Resource Costs is not working correctly via Job Services.
When using Job Services to schedule and Recalculate Resource Costs is selected, activity resource assignments that are set to Override are not recalculated based on the Override Price/Unit. The assignments are recalculated based on the Resource Price/Unit in the Resource dictionary.

Timescale

· prim46023: When formatting the Timescale, the Timescale Start Date acronyms are grayed out.
With the language set to French or German, Timescale formatting options are not enabled.

Timesheet Approval

· prim49311: Time approval hangs at 58%.
When a specific user tries to approve timesheets, the application freezes at 58%.

Undo

· prim41645: Undoing a Resource delete does not restore all resource information.
Performing an undo to restore a deleted resource does not restore all resource data, including resource assignments, timesheet actuals, and resource codes; only the resource itself is restored. Also, the message “Undo was not successfully completed. Please verify data” is displayed.

XER Import/Export

· prim46089: On XER import a large Notebook Topic entry is causing the import to take a long time.
When importing an XER file that includes a large Notebook Topic entry, the import takes a very long time.

Fixes from Previous Releases [return to top]

This service pack includes fixes from previous 5.0 service packs and hot fixes, as described below. For details, refer to the solution ID in the Primavera Knowledge Base.

Activities Reports

· prim22791: Timescale in report is shown differently depending on language settings.
· prim45408: Activities without predecessors appear in Out-of-Sequence activities list in Schedule Report.

Activities Screen

· prim26799: Out of bounds error when using the Resource Usage Profile.
· prim27897: Why doesn't the Activities screen refresh to show new activity code value assigned?

Activities View

· prim36819: The column headings in the Activities View do not convert the first time after changing the Set Language option to another language.

Activity Details Tabs

· prim27777: Completed activities display total float values.

Activity Leveling

· prim42448: Leveling not prioritizing the activities correctly.

Activity Relationships

· prim39670: Cannot edit activity Relationship Lag when accessing Project Management using the Compression Server.

Apply Actuals

· prim30813: Actual finish date removed from resource assignment when applying actuals.

Baselines

· prim25287: In a multi-user environment, updated baseline dates do not display as expected.
· prim26229: When using multiple filters to update a baseline, the ‘Show activities that match’ option continuously defaults to "All selected filters.”.
· prim26249: Baseline information occasionally disappears from the Activity table after updating a baseline.
· prim27158: When updating a baseline for added activities, the baseline data for the new activities does not display.
· prim33868: Event code errors generated when updating baselines.
· prim42993: Incorrect Project Baseline Bar translation for French and German.

Calendars - Activity, Resource, Project

· prim28845: Deleting a resource calendar sometimes deletes the resource.

Checking Project Integrity

· prim32313: 'EPS level' Activity code assignments are removed by 'Check Project Integrity'.

Codes - Project, Activity, Resource

· prim28325: Unable to assign some project codes via columns in the Projects table.

· prim22793: Activity code assignment filter for “Current project’s values” does not work when assigning codes through columns.

· prim22792: Activity code assignment not working when assigning values through column.

Compression Server

· prim37407: Compression Server client connection hangs with status “connecting to database”.

Constraints

· prim31547: Constraint time is set to 8:01am if a finish constraint is added to a finish milestone.

· prim29518: Removing the Expected Finish constraint sets Duration to 0.

Copy/Paste

· prim15837: Copying and pasting WBS elements creates duplicate activities.

· prim27579: Project Manager 4.0 provides a non-descriptive error message when copying and pasting projects that have duplicate activities.

· prim27825: Event Code error: AVAA0 displays and a duplicate project ID is created when copying and pasting a project.

Database Upgrade Program

· prim27447: Out of memory error occurs when upgrading to 5.0.

· prim27843: Database upgrade fails with error.

· prim28480, prim28482: Database scripts fail for setup /upgrade of databases.

Database Creation Scripts - Oracle, SQL, Interbase

· prim28131: ConfigAsst.exe fails when run against a German SQL database.

Edit - Fill Down, Select All

· prim22071: Selecting an EPS node and using Fill Down on the Data Date incorrectly displays the Planned Start Date.

Expedition Links

· prim27981: Event code error occurs when attempting to view Contract Management documents.

Global Change

· prim29812: Applying a global change on a set of activities deleted by another user creates orphaned user defined fields.

Job Service - Function

· prim28461: Running apply actuals through Job Services locks up the server.

· prim30831: Error occurs when scheduling a job to run while another job is running.

Language Support

· prim27472: Cannot create new Oracle or SQL databases, or install Job Services on Japanese Windows 2003 Server SP1.

Layouts

· prim29782: Changes to row height are lost after hitting File, Refresh.

· prim34395: Intermittent AVAA0 errors when changing layouts in Primavera Project Management 5.0.

Leveling

· prim9574: Activity with “Late as possible” constraint moved back to the DD after leveling.

Licensing

· prim28300: Error occurs when trying to administer license with any non-English Regional Setting.

· prim30855: Incremental license file does not increment the database with the additional licenses when being loaded into version 5.0.

Methodology Management Module

· prim34529: Error: “Table not found: ROLERATE” when exporting roles from Methodology Management.

MPP Import/Export

· prim23603: Importing an MPP file with no resource assignments increases the labor units by a factor of 100.

· prim33393: Material resource assignments spread incorrectly when imported from MS Project.

· prim35842: After importing from MS Project, earned value and performance percent complete are 0.

· prim37911: WBS summary activities imported from Microsoft Project showing units multiplied by 100.

Notebook Topics Reports

· prim31662: Notebook text is cut off Notebook topics report.

Performance

· prim28133: Poor Performance with Copy/Paste.

· prim28846: When undoing the deletion of a resource assignment the undo process takes a long time to complete.

· prim34653: SQL Server Performance Issues in version 5.0.

· prim36285: Deleting WBS nodes is slow in Project Management version 5.0 on MS SQL Server.

· prim36454: Report Wizard takes over 1 minute to display the additional subject area screen.

· prim36682: Performance degradation accessing Time Approval dialog box from 3.5.1 to 5.0.

· prim38164: Update Baseline Performance Improvements in 5.0 Service Pack 2.

· prim38176: Primavera 5.0 performance issues.

· prim39537: Why is performance slow when storing period performance with multiple projects open?

· prim44025: Summarization of projects takes an inordinately long time to complete or hangs halfway.

· prim46750: When logging in, the process hangs at 32%.

· prim48771: When logging in, the process hangs at 68%.

· prim42042: When logging in, the process hangs at 98%.

Printing

· prim29811: Communication error occurs when printing.

· prim29901: Event code: GPTWI-2179-9 when printing from Print Preview or File, Print.

· prim30369: Saved JPEG does not look like Print Preview when copied to Word/Excel.

Project

· prim29427: Errors occur when making a change in the current project and then opening another project.

· prim35930: VTRTA-2369-C error opening more than 1000 projects in Project Management module.

Project Architect

· prim27285: Event Code error VTFRN-1430-5 displays when importing linked base and plug-in methodology containing UDFs via Project Architect.

· prim28534: Application Event Code Error: “VQCVD-0692-1” or “VTDCF-2850-2” when running Project Architect.

· prim45749: Project Architect Fails with AVAA0-0889-7.

Project Manager - General

· prim30772: The password textbox does not display as expected during login.

Purging Deletions

· prim34642: Purge Deletes is not removing data from tables.

· prim40426: Error when purging deletes: CLEANUP_LOGICAL_DELETES Error: ORA20000: ORU10028: line length overflow, limit of 255 chars per line.

P3 Import/Export

· prim36672: Errors when exporting from Primavera Project Management 5.0 to P3 format.

Reports

· prim24658: Actual Finish field is incorrect when running a summary Resource Assignment Report.

· prim29733: Report columns not aligning for .html output.

· prim29739: Time distributed reports saved to a .csv format are not formatted properly.

· prim32709: Report Editor report changed to Report Wizard report after upgrading from 3.5.1 to 5.0.

Resource Assignments

· prim31611: Cannot replace resource assignment when activity is active on a timesheet with no hours assigned.

Resource Roles

· prim36495: Cannot change role because previous role already has actuals.

Risks

· prim26643: Risks View freezes when Control Tab is selected.

Scheduler

· prim28848: Access violation errors occur when scheduling a project.

· prim29352: Expected finish date ignored when scheduling if predecessor activity has finish to finish relationship.

· prim29745: Units for driving resources assigned to Level of Effort activities are not allocated correctly.

Security

· prim27833: A user with the Global Security option “Edit Global Reports” unchecked can edit and save a global report.

· prim30423: Unable to view global calendars when the security to edit global calendars is unchecked.

· prim31737: Cannot log into Project Management after changing application user's password successfully via dbconfig.

· prim31245: Unable to modify time periods in User Preferences despite the Admin Preference settings for "Allow users to specify the number of work hours for each time period" being enabled on the Time Periods tab.

· prim33178: Users can modify the Price/Unit rate on the Prices tab of the Roles dialog box for any role, even if they only have view privileges.

Setup

· prim27472: Cannot create new SQL database on Windows 2003 Server SP1.

Timesheets

· prim27834: A Resource's Timesheet is not visible in Time Approval.

· prim33477: Timesheets set to “RM Approved” when the option “Project Manager must approve before Resource Manager” is enabled.

· prim34905: Timesheet status is RM Approved but activities are in a state of Not Submitted.

· prim36195: VTFIO-1023-5 error when trying to print a timesheet report.

Tracking View

· prim37806: AVAA errors when refreshing (F5) or switching from roles to resource (or vice versa) in Tracking View if many/all projects are open.

Translation

· prim30058: Text is not translated in Excel export wizard.

· prim35163: Untranslated IDs displayed when regional settings are Czech.

· prim41973: Error in the German Translation file (comStrings.de-de)

· prim45364: Hint Help is only partially in French when the language has been set to French .

Users Dialog Box

· prim38170: Slow performance accessing the Version 5.0 User Profile.

WBS - Detail Tabs

· prim30803: Child WBS status not changed when project status changed by cut/paste.

XER Import/Export

· prim16871: Error when importing an XER file with orphaned User Defined Field records.

· prim22467: CVRJC-3802-1 event code when importing an XER file.

· prim26103: When importing relationships in spreadsheet (XLS) format, the relationship type sometimes appears blank.

· prim36825: Activity code values are duplicated after importing an XER file.

· prim45874: How to Import XER file using Command line parameters.

XLS Import/Export

· prim30051: Export Activity Relationships to Excel, when Regional Settings are set to some European countries, causes Lag to be multiplied by 100.

· prim30351: Negative values are not exported to XLS format.

Files Included with the Patch [return to top]

PM.exe, actions.xml, de-de-h1.dll, de-de-h2.dll, de-de-h3.dll, fr-fr-h1.dll, fr-fr-h2.dll, fr-fr-h3.dll, W32MKDE.EXE, W32MKRC.DLL, W32MKSET.DLL, W32MKSET.EXE, W32MKSET.HLP (C:\Program Files\Primavera\Project Management)

MM.exe (C:\Program Files\Primavera\Methodology Management)

PA.exe (C:\Program Files\Primavera\Portfolio Analysis)

P330XERConvert.exe, XERP330Convert.exe (C:\Program Files\Common Files\Primavera Common\Convert)

dbconfig.exe, dbcfglib.dll (C:\Program Files\Primavera\Common\bin and C:\Program Files\Common Files\Primavera Common\dbconfig depending on your configuration)

BREBootStrap.xml, INTERNAL_PLUGINS.XML (C:\Program Files\Common Files\Primavera Common\Java)

intgserver.jar, serializer.jar, xalan.jar, xerceslmpl.jar, xml-apis.jar (C:\Program Files\Common Files\Primavera Common\Java\lib)

PrmJob.exe, PrmJobSv.exe, PrmJobSvStrings.dll (C:\Program Files\Common Files\Primavera Common\JobService)

Language files: comCaptions.de-de, comCaptions.en-us, comCaptions.fr-fr, comCaptions.ja-jp, comCaptions.ru-ru, comCaptions.zh-cn, comCaptions.zh-tw, comStrings.de-de, comStrings.en-us, comStrings.fr-fr, comStrings.ja-jp, comStrings.ru-ru, comStrings.zh-cn, comStrings.zh-tw (C:\Program Files\Common Files\Primavera Common\Languages)

Help menu suggestion files: ru-rusuggest.doc, ru-rusuggest.htm, ru-rusuggest.txt, ja-jpsuggest.doc, ja-jpsuggest.htm, ja-jpsuggest.txt (C:\Program Files\Primavera\Common\suggest)

prm-updatebaseline.jar (C:\Program Files\Primavera\Project Management\Baseline Update)

dbexpsda.dll, DbExpPrC.dll (C:\Windows\System32)

Database Upgrade Instructions [return to top]

Before Proceeding

- If you have already installed Project Management Module Release 5.0 SP3, you do not need to perform any Primavera database upgrade. Go to Applying the Patch.

- If you have not already installed Project Management Module Release 5.0 SP3, use the following table to determine how to start your upgrade.

If you are upgrading from 3.5.x or 4.x to 5.0 SP4, first do the following to upgrade to the 5.0 base release:

1. Do one of the following, based on your SQL Server configuration:

- If you are running SQL Server on Windows 2003 or XP Professional with Data Execution Prevention (DEP) turned on, upgrade your Project Management database to 5.0 using the Automatic Database Upgrade Wizard (ConfigAsst.exe) that can be found in the \Database directory on the 5.0 SP1 Remastered release CD 1 disk. Please consult the Primavera Administrator’s Guide on the Documentation CD for instructions on Automatic Database Upgrades (Part 4: Page 345).

- If you are not running SQL Server on Windows 2003 or XP Professional with Data Execution Prevention (DEP) turned on, upgrade your Project Management database to 5.0 using the Automatic Database Upgrade Wizard (ConfigAsst.exe) that can be found in the \Database directory on the 5.0 release CD 1 disk. Please consult the Primavera Administrator’s Guide on the Documentation CD for instructions on Automatic Database Upgrades (Part 4: Page 345).

2. Once you complete this step, go to Step 2 – Upgrading Your Project Management Database from a Prior 5.0 Release to the 5.0 SP4 Release.

To upgrade your database, do the following:

1. Perform a cold backup of your current database, and, for an Oracle database, a full database export.

If you are unsure how to back up your Oracle database, do not proceed with the upgrade. Contact your database administrator, your database vendor, or Primavera Systems for assistance in backing up your database before performing the database upgrade. Also, ensure that you are familiar with the process of restoring the backup copy of the database in case you need to do so.

2. Download or copy the database update zip file (50SP4_DBFILES.ZIP), and extract its contents.

3. Double-click CONFIGASST.EXE to start the wizard.

4. Follow the steps in the wizard to upgrade your database. For details on using the wizard, see the “Automatic Database Upgrade” chapter in the Primavera Administrator’s Guide.

5. Verify that the proper schema has been applied. From the Project Management module, click Help/About Primavera. On the System tab, scroll down to Components and verify that the schema version is PMDB,0500.0024.0001.0006.

Note that the Methodology Management database schema is not updated as part of this service pack. It’s schema version should be MMDB,0500.0024.0001.0001.

6. Optional: the Project Management module uses Hierarchical queries during login. If login performance is degraded, after upgrading your database set the following Oracle initialization parameter at the database level to improve performance:

_old_connect_by_enabled = TRUE

7. Once you complete this step, go to Applying the Patch.

Applying the Patch and Download File [return to top]

Before Proceeding

- If you have already installed Project Management Module Release 5.0 SP3, go to Moving from 5.0 SP3.

- If you have not already installed Project Management Module Release 5.0 SP3, go to Moving from 5.0 SP2 or Earlier.

Moving from 5.0 SP3

Before you begin, verify that the proper schema has already been applied. From the Project Management module, click Help/About Primavera. On the System tab, scroll down to Components and verify that the schema version is PMDB,0500.0024.0001.0006. The Methodology Management database schema was not updated as part of SP3; it’s schema version should be MMDB,0500.0024.0001.0001. If your schema versions are different, follow the procedures in Database Upgrade Instructions, above, before continuing.

If you have already installed Project Management Module Release 5.0 SP3, to update each client workstation, do the following on every client machine:

1. Close all Primavera client applications.

2. Download or copy the patch zip file 50SP4_INSTALLFILES.ZIP (Download file here), and extract its contents, which includes the setup.exe file.

3. Run the setup program and follow the steps presented by the installation wizard.

Moving from 5.0 SP2 or Earlier

If you performed the Database Upgrade Instructions above, do the following to update each client workstation and any machines running Primavera Job Service:

1. Close all Primavera client applications and stop the Primavera Job Service (if it is running) from the Windows Services dialog box.

2. If Job Service is installed on this machine, move the existing file PrmJobSv<DB_Alias>.exe to a backup directory of your choice.

Note: PrmJobSv<DB_Alias>.exe is located in the following default location: C:\Program Files\Common Files\Primavera Common\JobService

3. Download or copy the patch zip file (50SP4_INSTALLFILES.ZIP), and extract its contents, which includes the setup.exe file.

4. Run the setup program and follow the steps presented by the installation wizard.

5. If Job Service is installed on this machine:

a. Make a copy of the following file:

\Primavera Common\JobService\PrmJobSv.exe (this newly updated file has a version 5.0.2000.14).

b. Rename Copy of PrmJobSv.exe to PrmJobSv<DB_Alias>.exe (it should use the same name as the file that was moved in step 2).

c. Start the Primavera Job Service (DB_Alias) from the Windows Services dialog box. To do this, select Primavera Job Service (DB_Alias), right-click, then choose Start.

Upgrade Instructions for SQL Server 2005 and Download File [return to top]

To upgrade to SQL Server 2005, download and extract the database file 50SP4_DBFILES.ZIP (download file here), then do one of the following, after applying the patch:

· Moving from SQL 2000 to SQL 2005: If you are moving your database from SQL Server 2000 to SQL Server 2005, see prim52689 in Primavera’s Knowledge Base for details.

· Creating a SQL 2005 Database: Run ConfigAsst.exe from the extracted database folder, and see the “Automatically Installing a SQL Server Database and Loading Application Data” topic in the Primavera Administrator’s Guide for details.

Improving Oracle Performance [return to top]

To improve Oracle performance, after applying the patch log in to the PMDB database as an administrative user (such as ADMUSER) and run the following scripts.

* Oracle 9.2 only, run gather_stats.sql to produce more comprehensive and accurate statistics.
* On any supported level of Oracle, also run querylib.sql to improve query performance for the Activity code table (ACTVCODE), deleted data table (REFRDEL), and UDF values.

Using the Command Line Import Feature [return to top]

To use the Windows command line interface to import an XER file (see prim45874), do the following:

1. Make a copy or edit the actions.xml file to specify the EPS you want to import the project to, the layout you want to use, and the XER file you want to import from.

You can specify more than one import action in a single file, by including multiple <action> nodes.

The following is a sample actions.xml file that illustrates importing 2 XER files from the same script. All tags must appear in the file; however, you can leave some tags empty, as noted below. Values in bold are literal values you must enter as is. Values in italics are samples that will vary with your configuration.

<type>import</type>

<importFormat>XER</importFormat>

<importType>PROJECT</importType>

<importAction>CREATE</importAction>

<importTo>EPS1</importTo>

<importConfiguration>MyConfig1</importConfiguration>

<importFile>c:\somefile1.xer</importFile>

</action>

<action>

<type>import</type>

<importFormat>XER</importFormat>

<importType>PROJECT</importType>

<importAction>CREATE</importAction>

<importTo>EPS2</importTo>

<importConfiguration>MyConfig2</importConfiguration>

<importFile>c:\somefile2.xer</importFile>

PM.EXE /username=<name> [/password=<name>]
[/alias=<name>] /actionScript=<path> [/logfile=<path>]

PM.EXE /username=admin /password=admin /alias=PMDB
/actionScript=c:\somefolder\importprojects.xml /logfile:c:\somefolder\myLog.txt

If any values include spaces, enclose the value in double quotes (“”). For example:

PM.EXE /username=admin /password=admin /alias=
PMDB /actionScript=”c:\some folder\importprojects.xml” /logfile=”c:\some folder\myLog.txt”

Processing results are written to the log file, or you can echo them to the command line interface.
Possible results are:

0 = success
1 = invalid alias
2 = invalid username or password
3 = XML file not found
4 = invalid action type (did not specify CREATE)
5 = insufficient security privileges
6 = failure while processing the import action. Could include invalid or missing values in the xml file.
214783647 = unhandled exception, including invalid characters

- If the command does not include all the required parameters, the PM module opens.

- The import action:

1. Creates only new projects; you cannot update an existing project.

2. Creates multiple projects under the same EPS if there are multiple projects in an XER file;
you cannot filter out specific projects within an XER file.

3. If you include non-English characters in the XML file, use the XML encoding attribute to
specify the language, prior to the <actions> tag. For example, to specify German or French encoding:

<?xml version=”1.0” encoding=”windows-1252”?>

Also, be sure to save the XML file as Unicode.

The following languages are supported by the Project Management module:

Copyright © Primavera 1999-2008. All rights reserved.