An attribute created as a 'lookup - number' is not displaying the value in List view. But it holds value in Edit Layout.
Tried to remove and readd the field to the list view. But no help.
Any suggestions or tips...
Thanks in advance,
So parametrised lookups don't work in List views, but this was meant to be fixed in 13.3 (see below).
Try de-activating the attribute and then re-activiating it?
Tried your suggestion. Deactivated and activated the field, added fields to the Layouts. But no help.. Fields is displaying data in Edit Layout, but not in List Layout.
Is the field on a secure subpage? Does the user only have "edit" rights to that secure subpage (and not "view" rights). Sounds daft I know but I am GUESSing here.
Yes, Dave I understand, its little weird issue. The field is not in secure page and I'm using admin user.
Can you please let me know in which List View you actually want to see the column data but, somehow, you are not able to see that? (For example, Project List, Tasks List etc.)
Hi Abhisek, Object is a custom object, and I'm trying to display its attribute.
There is a documented BUG CLRT-74942 where the columns do not show values for Resource Utilization portlet once they are configured to view after "Weekly schedule" column.
See the steps to reproduce as below:
1. Create a Project in clarity and add few task
2. Create a base line and save
3.. Go to Resource Utilization Portlet and configure Baseline Start & Baseline Finish attribute after Weekly Schedule
Expected result: The baseline start and baseline finish date should appear
Actual result: The baseline start and baseline finish date doesn't appear
I am not sure but still let me know if this is something similar to what you are facing.
Which version of Clarity are you using? Is the Field a multiselect or a single select. If my understanding is right prior to 13 it is not possible to add multiselct lookup fields in the List view.
Hi Teena.. Thanks for the reply. The field is not a multiselect and I'm into v13.3
What is the Attribute Value Protection Setting for that list view, You can see it via object -> views. Try setting to the last value and see if that helps.
You can use this query to check how much attribute value protection is being used - select use_display_conds_for_security , count(1) from CMN_GRIDS group by use_display_conds_for_security If the majority of the views have their display conditions field set to 1, then it would be a systemic problem You can use the below query to correct AVP settings on objects: update cmn_grids set use_display_conds_for_security=0 where id in (select id from cmn_grids where principal_type='SYSTEM' and (USE_DISPLAY_CONDS_FOR_SECURITY=1 or use_display_conds_for_security=2) and dal_type='object'); You can use the below query to correct AVP on personalized object views for users: update cmn_grids set use_display_conds_for_security=0 where id in (select id from cmn_grids where principal_type='USER' and (USE_DISPLAY_CONDS_FOR_SECURITY=1 or use_display_conds_for_security=2) and dal_type='object'); These queries both set the AVP value to "subpage security only", which is how it should be
We had a similiar issue last fall. In our case it was an attribute that was on a couple of different pages and we had it on one secure page. AVP is what was causing the issue. We changed the AVP setting to: use only secured subpages to protect attribute values on this list. it solved the problem. It was the display condition that we had enabled on one section of a subpaage that create the issue were we could not look at the attribute in the list view.
From CA World 2011: pp302sn_Performance_CA.pptx had a slide on AVP i'll upload.
Here is the PPT from the CA World 2011
Hi Mike, Sorry for the delayed response. The document which you shared was good. Our attribute setting is "Display all attribute values on this list" and there are no secured pages & display conditions. The issue on the object list view appears in PROD environment only and not in any other environment. Also i tried changing the AVP settings, but still didn't help.
Is the attribute a parameterised lookup?
Yes Dave, Its a parameterised dynamic query lookup.
Dave, Finally, that had some thing to do with . I added the parameter NULL condition in to the query, but the value didn't display in list view. And when i revoked back the parameter NULL condition from the query, it started displaying the value in list view . I guess some glitch happened while saving the lookup.
Retrieving data ...