Fields with Lookup unreadable when a Field has custom name
Multi platform library to read and write schedule data
Brought to you by:
joniles
Menu
▾
▴
1 Attachments
#324 Fields with Lookup unreadable when a Field has custom name
The current version of MPXJ (7.2.1) seems to refuse to read Lookup fields when I change a field to have a different name.
For example, create a new project, show Text1, set it to Lookup, add 0 and 1 to the Lookup list, and rename Text1 to anything ('Test'). Now generate a task and set it's Text1 (Test) to 1.
Now you can't read the 1 in Text1 (task.getText(1) returns null).
I didn't realize posting a file would prevent me from editting the ticket before submission. I've attached a file with the problem. Notice that renaming Text1 back to empty/blank fixes the problem.
The changes to fix this issue are now available on GitHub and will form part of the next MPXJ release (probably within the next week).