#35 Import of OWB-generated XML incorrect

[kaptijnr]

Try the following:
New project, one task, one resource. Assign resource to
task for 25 hours.
Create a view with ETC and actuals per day.
Autoschedule:

Fri Sat Sun Mon Tue Wed
ETC 8 0 0 8 8 1
ACT 0 0 0 0 0 0

Save as RMP and XML, open XML file:

Fri Sat Sun Mon Tue Wed
ETC 80 0 0 80 80 10
ACT 0 0 0 0 0 0

Reopen RMP, now book actuals: 4, 3 and 1,5 hours and
autoschedule:
Fri Sat Sun Mon Tue Wed Thu Fri
ETC 0 0 0 0 0 8 8 1
ACT 4 0 0 3 1.5 0 0 0

Save as XML, open XML file:
Fri Sat Sun Mon Tue Wed Thu Fri
ETC 0 0 0 0 0 80 80 1
ACT 40 0 0 3000 15000 0 0 0

I think the XML element Curve/Segment import screws
things up completely !

This makes it hard to write converters via the XML-
format...

Rene Kaptijn
ICT Embedded

[owb_support]

Logged In: YES
user_id=1114192

This happens when the regional settings are set so numbers
are displayed as 1,0. The xml export is exporting numbers as
1.0. When imported some number values are not correct,
such as estMax 1.0 imports as 1000. Assignment rate of 1.0
will import 8 hours etc as 80,00.

Work around for now is to edit the xml file so estMax is 1,0
and assignment rate is 1,0.

[owb_support]

Logged In: YES
user_id=1114192

Niku Tracking Number 75389.

[kaptijnr]

Logged In: YES
user_id=1224946

The same problem applies to the project budget...

[Nobody/Anonymous]

Logged In: NO

This bug actually prevents usage with XML files completely, at
least for the German version. After every re-opening of an XML,
all estimates are unusable. IMHO this is a top priority bug, as
OWB suggest saving in XML.
Nevertheless it seems to avoid this problem by saving in RMP.

[cmogentale]

Logged In: YES
user_id=1542367

i encountered the same problem. it seems to be linked to the
rate value in the segment tags. if this rate is inferior to
1 the value calculated from this segment is not taken into
account => matters come with resource with an availability
different from 100%

[Anonymous]

Logged In: YES
user_id=968512

The bug can be fixed by adding an if-statement in
AppServer.jar. This jar-file is located in the lib folder of
Open Workbench.
For modifying it you need to download the source code of
Open Workbench. Besides you need to have a Java SDK (= 1.4;
you get problems with java versions > 1.4) installed. You do
not need anything else!!!

At first change the JAVA_HOME and WORKBENCH_HOME settings in
the file workbench.properties.
Then place the following code into
com.abtcorp.io.client.xmlfile.exporters.owb.XMLFile.java#writeAttribute:
if ((name.compareTo("estMax") == 0) ||
(name.compareTo("rate") == 0)) {
value = value.replace('.', ',');
}
Place the code in front of the "out_.write( name );"-statement.

Then run the build-file with the target -buildappserver. By
doing so you create a new AppServer.jar. Copy this file into
your lib-folder and the bug is fixed!

[Anonymous]

Logged In: YES
user_id=968512

Comment to my comment :)
You also need Apache Ant installed in order to run the
build-file.