Web Component customization issues

Hi all,

I'm doing customization to the web client of WorkSite MP 4.1 SP1 and now having the following issues:

1. I added a new date type field to the Task profile and the Task List. By default, the Task List is sorted on the Due Date column. I want to changed it to sort on the new column by default, but it doesn't work. Here is what I did to change the default sort value:
- changed the paremeter sortValue of Task List from ${task.dueDate} to ${task.extTask_date} (the new field)

2. I added a new Metadata type field to the Issue profile and Issue List. The new column of Issue List shows correct data, but the workspace page shows error message "Bundle failed, please see log for details" at the bottom. If I remove the new column, the error will be gone. Please note that this is not an issue when adding a new field with type other than Metadata type (e.g. char, varChar) to the Issue List. I checked the WorkSite log file and got the following message:

--------Log------
Context: None
Details: Failed to evaluation expression: ${data.issue.extIssue_type.id}, attribute: value
Action: None
com.imanage.workteam.exceptions.JspExpressionEvalException:Failed to evaluation expression: ${data.issue.extIssue_type.id}, attribute: value(javax.servlet.jsp.JspException:An error occurred while evaluating custom action attribute "value" with value "${data.issue.extIssue_type.id}": Unable to find a value for "id" in object of class "java.lang.String" using operator "." (null))
Underlying StackTrace:
javax.servlet.jsp.JspException: An error occurred while evaluating custom action attribute "value" with value "${data.issue.extIssue_type.id}": Unable to find a value for "id" in object of class "java.lang.String" using operator "." (null)
------Log----

The new field is called Issue_type.

Any ideas on how to solve the problem would be very appreciated.

Simon

Find more posts tagged with

Comments

Migrateduser

I wonder if the same will happen if you remove underscore from your EXT field names? If that fixes it, I would call it a bug.
I assume your EXT fields has id column as well as name and description columns?

ihssimon

Thanks for your opinion. The Issue_type metadata table only has a name column. WorkSite creates an internal ID column (x_sid) for each metadata table. I will try to create some new fields without underscore to see what will happen.