Clarity

  • 1.  Parameterized lookup causing issue when audited

    Posted Dec 18, 2015 05:37 AM

    Hi Team,

     

    1) 'Param' is custom field in Project object.

    2) Custom object 'A' is child object of Project object and Virtual attribute 'Param' is added into custom object 'A'.

    3) There is custom attribute 'ABC Target' in object A, which is parameterized lookup and the parameter 'Param' passed to this field.

     

    We are populating some data into instances of object A using process.

    If the field "ABC Target" is Audited, the instance of A never populates the data after process is completed and the log of process shows error "com.niku.union.odf.exception.ODFException: com.niku.union.service.ServiceException: Unable to update instance 5058001 for object A".

    and if the field "ABS Target" is removed from audited attributes, instance of object A populates the data from same process without above error.

     

    I have tried re-xogging the lookup of attribute "ABS Target", but that never helped.

     

    Has anyone observed this error before? Any solution/Workaround for this option?

     

    Br,

    Sandeep



  • 2.  Re: Parameterized lookup causing issue when audited

    Posted Dec 28, 2015 12:47 AM

    Has anyone observed this error before? Any solution/Workaround for this?



  • 3.  Re: Parameterized lookup causing issue when audited

    Posted Jun 06, 2017 09:14 AM

    Yes, we also observed a similar issue recently. Any idea how to overcome this?



  • 4.  Re: Parameterized lookup causing issue when audited

    Posted Jun 06, 2017 09:22 AM

    Clarity: Audit trail shows no value for parameterized lookup

    Document ID:  TEC595088
    Last Modified Date:  08/07/2015
    Show Technical Document Details

    Description:

    Audit trail is blank for old and new values populated for dependent lookups

    Steps to Reproduce:

    1. Create a static "lookup_01" with a list of static values,
    2. Using NSQL create a dynamic lookup "lookup_02" so that the selection of the value is driven by the selection of the first lookup "lookup_01"
    3. Create 2 new attributes "Field One" and "Field Two" for an object, such as the Project object
    4. Use lookup "lookup_01" for "Field One", and "lookup_02" for "Field Two"
    5. For attribute "Field Two", create mapping to "Field One" under 'Lookup Paremeter Mappings" on its Object Attribute properties page
    6. In the object's Audit Trail page, add "Field Two" for audit upon Update
    7. Open an instance of the object, for example, a project, and navigate to a view where "Field One" and "Field Two" are configured
    8. Select a value for "Field One", then select a value for "Field Two", Save
    9. Select a different value for "Field Two", Save
    10. Examine the entries on Audit Trail tab for "Field Two"

    Expected Result: There is a row for Attribute Name of "Field Two", Operation is "Update", both Old Value and New Value are shown with the values chosen from step 7 and 8
    Actual Result: There is a row for Attribute Name of "Field Two", Operation is "Update", both Old Value and New Value are blank

    Solution:

    WORKAROUND:
    None.

    STATUS/RESOLUTION:
    CLRT-69366 : No plans to fix.
    For more details please review the Customer Reported Defect Resolution Policy for Clarity.

     

     

    NJ