You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/guides/msp-export-module-whatsnew.md
+36-34Lines changed: 36 additions & 34 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,59 +3,61 @@ title: "What's new in MSP Project Export Module"
3
3
sidebar_label: "What's new in MSP Project Export Module"
4
4
---
5
5
6
-
# What's new in MSP Project Export Module
6
+
What's new in MSP Project Export Module
7
+
===========================================
8
+
9
+
## 2.3.0.0
10
+
11
+
- Updated MPXJ library to the 12.10.3 version.
12
+
- Added support for standard task types (Project and Milestone) out of the box. Milestones in Primavera have the `FINISH_MILESTONE` type
13
+
- Added support for Start and Finish Milestones for the Primavera export
14
+
- Added support for exporting all 11 Baselines to MSP files
15
+
- Added support for extended fields with different types: Number1-20, Flag1-20, Cost1-10, Date1-10, Start1-10, Finish1-10, Duration1-10, OutlineCode1-10
16
+
- Added support for using exact names for Text1-30 properties. Now, it works when you specify an alias ("My custom prop") or field name ("Text1")
17
+
- Increased the list of supported task properties in MSP files. Now, they are loaded as standard properties, not as custom/extended fields
18
+
- Added support for standard resource properties and extended fields: Number1-20, Flag1-20, Cost1-10, Date1-10, Start1-10, Finish1-10, Duration1-10, OutlineCode1-10
19
+
- Added a way to import most of the standard resource properties with a single property (so that you don't need to list all the properties)
20
+
- Fixed the resource export when assignments don't have the units value
21
+
- Fixed various errors that prevented file import and export because of some values in the task properties
7
22
8
23
## 2.2.1.0
9
24
10
-
• Fixed specifying 24-hour value as the working time config (for example, `gantt.setWorkTime({ hours: ["00:00-24:00"] })`)
11
-
12
-
• Fixed the returned Project calendar when specifying the `CalendarUID` property in the `projectProperties` parameter in the import functions
25
+
- Fixed specifying 24-hour value as the working time config (for example, `gantt.setWorkTime({ hours: ["00:00-24:00"] })`)
26
+
- Fixed the returned Project calendar when specifying the `CalendarUID` property in the `projectProperties` parameter in the import functions
13
27
14
28
## 2.2.0.0
15
29
16
-
* Updated MPXJ library to the 12.0.0 version
17
-
18
-
* Correct import of the `Start` and `Finish` properties specified in the `taskProperties` parameter
19
-
20
-
* Fixed import when specifying duplicate values in the `taskProperties` parameter
21
-
22
-
* Fixed import when specifying the `CalendarUID` property in the `taskProperties` parameter and a task doesn't have the calendar
23
-
24
-
* Fixed export when `gantt.config.worktimes` has an empty array
25
-
26
-
* Fixed export when specifying working time settings in the old format
30
+
- Updated MPXJ library to the 12.0.0 version
31
+
- Correct import of the `Start` and `Finish` properties specified in the `taskProperties` parameter
32
+
- Fixed import when specifying duplicate values in the `taskProperties` parameter
33
+
- Fixed import when specifying the `CalendarUID` property in the `taskProperties` parameter and a task doesn't have the calendar
34
+
- Fixed export when `gantt.config.worktimes` has an empty array
35
+
- Fixed export when specifying working time settings in the old format
27
36
28
37
## 2.1.1.0
29
38
30
-
* Renamed the property that contains calendars from `worktimes` to `calendars`
31
-
32
-
* Added a property that contains the ID of the global calendar
33
-
34
-
* Restored the `worktime` property that contains the global calendars settings for backward compatibility
39
+
- Renamed the property that contains calendars from `worktimes` to `calendars`
40
+
- Added a property that contains the ID of the global calendar
41
+
- Restored the `worktime` property that contains the global calendars settings for backward compatibility
35
42
36
43
## 2.1.0.0
37
44
38
-
* Added support for custom calendars for the imported and exported MSP and Primavera files (including resource calendars)
39
-
40
-
* Added support for getting resource assignment values from units when importing files
41
-
42
-
* Added support for specifying custom values for the resource assignment units when exporting files
43
-
44
-
* Added the **RemainingDuration** property for Primavera export to get the same end date for tasks without additional configuration
45
+
- Added support for custom calendars for the imported and exported MSP and Primavera files (including resource calendars)
46
+
- Added support for getting resource assignment values from units when importing files
47
+
- Added support for specifying custom values for the resource assignment units when exporting files
48
+
- Added the **RemainingDuration** property for Primavera export to get the same end date for tasks without additional configuration
45
49
46
50
## 2.0.2.0
47
51
48
-
* Updated MPXJ library to the 11.5.4 version
49
-
50
-
* Added support for custom properties of Summary (WBS) tasks for Primavera import and export.
52
+
- Updated MPXJ library to the 11.5.4 version
53
+
- Added support for custom properties of Summary (WBS) tasks for Primavera import and export.
51
54
It works even when properties have the same name. To make it work for the Summary tasks when you export the data, you need to return *true* for the **Summary** property.
52
-
53
-
* Fixed the bug when Baseline 0 wasn't imported
55
+
- Fixed the bug when Baseline 0 wasn't imported
54
56
55
57
## 2.0.0.1
56
58
57
-
* Various internal optimizations and imported Dockerfile
59
+
- Various internal optimizations and imported Dockerfile
58
60
59
61
## 2.0.0.0
60
62
61
-
* Migrated from ASP.NET MVC to ASP.NET core. So, now it is possible to run the MSP export module on Linux and inside the Docker image
63
+
- Migrated from ASP.NET MVC to ASP.NET core. So, now it is possible to run the MSP export module on Linux and inside the Docker image
0 commit comments