Mapping Task Priority between PPM and MSP

Document ID : KB000014516
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

Priority field in PPM is mapped to the Priority field in Microsoft Project. However, the available Priority range is different in both applications.  

Question:

How are the Priority values translated between the range (0-1000) in Microsoft Project and the range (36-0) in MSP? And what happens if I enter a value that is not on this list and attempt to save this value back from MSP to PPM?

Environment:
CA PPM 14.4, 15.1 and 15.2
Answer:

The following table lists the equivalent values for the Priority in both applications: 

PPM Priority

MSP Priority

 

PPM Priority

MSP Priority

 

PPM Priority

MSP Priority

36

0

 

23

361

 

10

722

35

28

 

22

389

 

9

750

34

56

 

21

417

 

8

778

33

83

 

20

444

 

7

806

32

111

 

19

472

 

6

833

31

139

 

18

500

 

5

861

30

167

 

17

528

 

4

889

29

194

 

16

556

 

3

917

28

222

 

15

583

 

2

944

27

250

 

14

611

 

1

972

26

278

 

13

639

 

0

1000

25

306

 

12

667

 

 

 

24

333

 

11

694

 

 

 

 

If a value that is not on this list is entered in Microsoft Project, it will save back to PPM with the nearest Priority to that value. For example, entering a Priority of 400 in Microsoft Project would save back to PPM as a Priority of 22. So when the project was exported to Microsoft Project again, the Priority that we would then see would be 389.