Versions Compared

Old Version 11

changes.mady.by.user priti.hota (Deactivated)

Saved on

compared with

New Version Current

changes.mady.by.user priti.hota (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

When working with Advanced Reporting, you may encounter the following issues:

...

Error While Adding Fields to Ad Hoc View

Symptom

When I you add fields to an ad hoc view, one of the following errors occur:

    • An error message displays.
    • Progress bar displays continuously without any action on the page.

Solutions

This error may occur for single or all fields. Use one of the following resolutions according to the requirement:

    • If the problem is with a specific field, do the following actions: 
      • Ensure that the field you add to an ad hoc view is properly converted to its actual data type in the domain. For more information about transformation expression, see step 8.c from Sync Custom Fields to Domain.
      • Ensure that the schema is designed properly such as Joins are proper, Derived Tables should have table hints and no long running queries.  
    • If the problem is with all the fields, contact Support.

...

Ensure that the ad hoc view or report name does not exceed more than 94 characters.

Error While Editing Domain

Symptom
      When you edit the domain in ad hoc view, clicking Check Design displays the following validation message:      

“The Domain schema is invalid. Review the schema.
The Domain schema has an invalid resource.
Filter condition dbo_VAM_ASSET_LIST.row_id references one or more fields, ID dbo_VAM_ASSET_LIST.row_id, that cannot be found.
Filter condition person2_lvl3_org_name references one or more fields, ID person2_lvl3_org_name, that cannot be found.
Filter condition dbo_VAM_ASSET_LIST.row_id references one or more fields, ID dbo_VAM_ASSET_LIST.row_id, that cannot be found.
Filter condition person2_lvl3_org_name references one or more fields, ID person2_lvl3_org_name, that cannot be found.”

Solution     
     Perform the following steps and click Check Design:

  • Update Asset_Id_Dupl calculated field Under VAM_ASSET_LIST table change the value from dbo_VAM_ASSET_LIST.row_id to dbo_VAM_ASSET_LIST.ROW_ID
  • Under VAPP_ITEM/DM_VAPP_ITEM - Delete the calculated field ‘contact_location’ from calculated field and display sections of domain

     You will get a banner saving domain design validation message as "Domain design was validated".  

Error While Opening Report

Symptom

When I you open a report that is created with custom fields, I receive an error.

...

Domain Security File Is Invalid

Symptom

When I you click Submit in the Edit Domain page after updating the domain, I receive an error stating that the domain security file is invalid.

...

This error occurs because of the mismatch of data set names with their corresponding Join Trees in the security file and domain. In the domain, the data sets are available under Display, Resources, Join Trees. 

To fix this issue, download and open the security file in your local computer. Compare the data set in the Join Trees between the security file and Resources pane. If the data sets are not matching with Join Trees, update the Join Trees in the security file to match with the Resources pane.

Follow these steps:

  1. Click and download the security file custom_cloud_sm_security.xml from the Edit Domain, Optional Information, Security File to your local computer.
  2. Click Edit with Domain Designer and access Domain Designer, Display tab. The Display tab opens with the list of Join Trees on the left pane under Resources.
  3. Open the downloaded security file in a text editor such as WordPad.

  4. Expand the Join Trees under Resources pane. Verify that the table names in all the Join Trees section and in the security file are same.
    For example, consider the following security file code:

    Code Block
    languagexml
    <resourceAccessGrantList id="Tasks_FilterList" label="Tasks Filter List" resourceId="JoinTree_1">
<resourceAccessGrants>
<resourceAccessGrant id="TaskSliceFilter"><principalExpression>(authentication.getPrincipal().getAttributes().any{
it.getAttrName() in ['nsd_slice']})</principalExpression> 
<filterExpression>(testProfileAttribute(dbo_VITPM_PROJECT_TASKS.slice,'nsd_slice'))</filterExpression> 
</resourceAccessGrant>
<resourceAccessGrant id="TaskMemberFilter">
<principalExpression>(authentication.getPrincipal().getAttributes().any{it.getAttrName() in ['nsd_UserId']})</principalExpression> 
<filterExpression>((groovy('authentication.getPrincipal().getRoles().any{it.getRoleName()=="ROLE_CSM_ADMINISTRATOR"}') == 'true') or
CHARINDEX(dbo_VITPM_PROJECT_TASKS.members,(groovy('authentication.getPrincipal().getAttributes().find{it.getAttrName()=="nsd_UserId"}.attrValue')))>=0)</filterExpression> 
</resourceAccessGrant>
<resourceAccessGrant id="Task_OBSFilter">
<principalExpression>
<![CDATA[authentication.getPrincipal().getAttributes().any{it.getAttrName() in ['nsd_OBSEnabled'] && it.getAttrValue() in ['True']}]]> 
</principalExpression>
<filterExpression>(OBS_PRJ_TASKS.org_id in (dbo_VITPM_PROJECT_TASKS.org_id) and testProfileAttribute(OBS_PRJ_TASKS.user_id,'nsd_UserId'))</filterExpression> 
</resourceAccessGrant>
</resourceAccessGrants>
</resourceAccessGrantList>

    The resourceId specifies the Joint Tree name as JoinTree_1 and the filterExpression specifies the table name as dbo_VITPM_PROJECT_TASKS. Verify that the table name dbo_VITPM_PROJECT_TASKS matches the table name in JointTree_1 under Resources pane.

  5. If the table names of the security file do not match with the Join Trees in the Resource pane, edit the security file accordingly.
    For example, consider the table name dbo_VITPM_PROJECT_TASKS is in the JoinTree_1 of the security file. In the Resources panel of the Display tab, the dbo_VITPM_PROJECT_TASKS table is available in JoinTree_2. To match the information, edit the security file and rename the resourceId value from JoinTree_1 to JoinTree_2.
    Change all the resourceId values in the security file, accordingly.  

  6. Save your changes and close the security file.

  7. Click Cancel to navigate back to the Edit Domain page.

  8. In the Edit Domain page, click Change corresponding to the security file. Browse and select the security file from your local computer.

  9. Click Submit. The old security file is replaced with the updated file and issue of invalid domain security file is resolved.

Requester's Organization Field Is Not Displaying Data

Symptom

When I you add the Requester's Organization field to a report, the subsequently generated report does not display data under Requester's Organization field.

...

Error While Converting Date Data Type

Symptom

When I you create an Ad Hoc view, an error is displayed while adding the custom DateTime column.

...

An error is displayed when I you add custom fields that contains accented characters to Ad Hoc views.

...