Skip to main content
insightsoftware Documentation insightsoftware Documentation
{%article.title%}
Published:
Was this article helpful?
0 out of 0 found this helpful

Best Practices

The best practices for Angles for Oracle-Views are as follows:

  • To avoid RPD generation issues, maintain separate instances to generate RPD for production and non-production environments.

  • If you face any VPN connectivity issues, please reach out to support.

  • Before adding joins to newly-created business views, ensure to deploy the business views.

  • When you create a custom view, ensure that NoetixViews schema has all the required privileges.

  • Ensure to refresh business views after upgrading the Angles Hub application.

  • If you run into any issues with the Angles Hub user interface, clear the cache.

  • When you change the NoetixViews schema password, ensure to update the NoetixViews schema password in Angles Hub.

  • When you revert a business view to the previous versions, the business view is saved automatically. You do not have to save the business view again.

  • The availability of circular joins will hinder RPD generation. Ensure that there are no circular joins in the business views.

  • If you want to add join conditions for any column, a proper column alias has to be
    provided in the SQL query of the business view.
  • If you’re adding filters to a report with the Report Type as Snapshot and want to apply a
    filter to a specific column, first ensure that this column is selected in the Report tab.
  • To generate the non-global personalized reports, edit the report, go to the Configuration
    tab and select the Generate option.
  • While adding filter expressions, if you are using views other than the main view, ensure
    to prefix the view with the schema name.
  • In the following filter expression, NV71_1757_RGR_DEV is added as a prefix to the
    APG0_LOV_ALL_DATES view:
    (select transaction_date from NV71_1757_RGR_DEV.APG0_LOV_ALL_DATES) and 
    (INVOICE_CREATION_DATE - INVOICE_DATE) > 60
  • Ensure that join columns are not deleted from the business views.
  • Ensure that the name of the non-compliance view (view without metadata) that is created
    directly in the database does not exceed 30 characters

 

 
Published:

Best Practices

The best practices for Angles for Oracle-Views are as follows:

  • To avoid RPD generation issues, maintain separate instances to generate RPD for production and non-production environments.

  • If you face any VPN connectivity issues, please reach out to support.

  • Before adding joins to newly-created business views, ensure to deploy the business views.

  • When you create a custom view, ensure that NoetixViews schema has all the required privileges.

  • Ensure to refresh business views after upgrading the Angles Hub application.

  • If you run into any issues with the Angles Hub user interface, clear the cache.

  • When you change the NoetixViews schema password, ensure to update the NoetixViews schema password in Angles Hub.

  • When you revert a business view to the previous versions, the business view is saved automatically. You do not have to save the business view again.

  • The availability of circular joins will hinder RPD generation. Ensure that there are no circular joins in the business views.

  • If you want to add join conditions for any column, a proper column alias has to be
    provided in the SQL query of the business view.
  • If you’re adding filters to a report with the Report Type as Snapshot and want to apply a
    filter to a specific column, first ensure that this column is selected in the Report tab.
  • To generate the non-global personalized reports, edit the report, go to the Configuration
    tab and select the Generate option.
  • While adding filter expressions, if you are using views other than the main view, ensure
    to prefix the view with the schema name.
  • In the following filter expression, NV71_1757_RGR_DEV is added as a prefix to the
    APG0_LOV_ALL_DATES view:
    (select transaction_date from NV71_1757_RGR_DEV.APG0_LOV_ALL_DATES) and 
    (INVOICE_CREATION_DATE - INVOICE_DATE) > 60
  • Ensure that join columns are not deleted from the business views.
  • Ensure that the name of the non-compliance view (view without metadata) that is created
    directly in the database does not exceed 30 characters

 

 
For an optimal Community experience, Please view on Desktop