[mgreenberg]

Thanks for looking into it.

We actually changed our backend db to return status IDs (0, 1 and 2 for the ordinal values) instead of status strings but still wanted strings to be displayed in the UI and hence using enum ordinals. We sort based on these IDs in our back-end SQL, not on the strings.

Anyways, thanks for your input and I look forward to your response.

[Isomorphic]

In that case, note that you can just declare the field as "int" and hand-code the valueMap as a workaround. Then the enumTranslateStrategy won't be needed. But we'll let you know if we uncover a bug here.

[mgreenberg]

Ok, thanks. I am hoping you can get back to me soon on whether this is a bug. For using ints, I have to rewire everything to use ints instead of enums again including the DAOs, bean and our tests.

[sabaka]

Yes, this was a bug. relatedUpdates were ignoring DataSource.enumTranslateStrategy setting. It is fixed now.

[mgreenberg]

Great, thanks!

Did you get a chance to check on the other issue too (from post #3) where the mapped string values for the enum are aligned to the right instead of to the left?

I also noticed another minor issue. When a value for the Status data source field is the ordinal with value 0 ('Unresolved'), it displays the value fine in the column as expected, but when I pull down the drop-down, 'Unresolved' is not highlighted in the drop-down. If the field value is any other value such as 'In Progress' (ordinal 1) or 'Resolved' (ordinal 2), the value is selected. Would this be a bug? See attached.

[Isomorphic]

We've made some changes to address both of these issues. Please try the next nightly build (dated Aug 29 or above), in the 3.1p, 4.0p or 4.1d branch.

Regards
Isomorphic Software

[mgreenberg]

Thanks Isomorphic. I will try this out the next time we do an update and see if it fixes the issues.