Unable to achieve consistent look on Status report with refence to Lookup's hidden key (lookup_enum or lookup_code)
Article ID: 396405
Updated On:
Products
Issue/Introduction
In the Status module we are trying to display custom attribute lookup value in two lines to standardize the same look as the out of box Schedule Status or Scope Status attribute look. The out of box lookup hidden key=lookup_enum, however the custom lookup hidden key=lookup_code by default. When changing the custom lookup hidden key to lookup_enum this seems to fix the text wrap issue and removes the scroll bar to achieve the same look. What is the difference between using lookup_code versus lookup_enum? Could these adjustments potentially affect the values when we generating reports in PowerBI?
Environment
Any Clarity release
Cause
This is caused by DE169950.
Resolution
While using lookup_code versus lookup_enum has no downstream implication on report generation or power BI (in either case what will be displayed is the lookup value, which is 'Deviation Recovery' in your example), We can't make a blanket comment that the web is correct for either code or enum as data truncation in UI (and exported pdf for the status report) is still possible for really long lookup values as shown in the call where we used an example lookup value 'JustJustJustJustJustJustJustJust for Validation' to show how it does not fit within the widget minimum width.
After a careful review, this functionality will not be changed at this stage. If needed Product Management and UX will have to come up with a feature to enhance this for web and have a consistent treatment irrespective of lookup_enum or lookup_code.
Please attend the Product Management Office Hours to discuss further plans on this.
Feedback
