|
Release Notes TPG PSLink 2022 > Version 9.4.1.0 |
For assignments and task links, we've seen it often that Project Server does not provide us with the full object information. Concretely, for an assignment we sometimes do not get the necessary task or resource information, which then caused an error with the message:
The property or field 'Id' has not been initialized. It has not been requested or the request has not been executed. It may need to be explicitly requested.
For task links, typically the successor information is missing. The corresponding error message was then:
Object reference not set to an instance of an object on server. The object is associated with property End.
The affected assignments and task links are valid and displayed just fine in Project Professional and PWA, and at the same time they are somehow defective such that Project Server is not able to provide all information about the respective object to us.
In the new release, we have at least improved the error messages. From now on, the affected assignment or task link is pointed out in the error message such that users can identify, remove, and recreate those.
Here we had also a message which popped up every now and then: When an error occurred trying to execute an action, sometimes one would only get the following error in the log:
Expression could not be compiled. Cannot evaluate constant expression: PropertyBinding.GetValue() threw an exception.
The underlying error was missing in that log message. For technical reasons that is still the case, but to simplify diagnosis we're writing the underlying error to Windows Event Viewer now. So when you encounter that error the next time, remember to check Windows Event Viewer for details.
Our GetJiraIssues action was not designed to support multiple custom fields with the same name. Due to this, you could see some strange and seemingly unrelated errors when reading issues from Jira systems with such a configuration.
In the new version we have fixed this. When we detect multiple custom fields with the same name, we're assigning stable names to them by adding a numeric suffix. Thus, you'll see custom field names like "MyCustomField" (without suffix) and "MyCustomField2" (with numeric suffix) in a single table.