Skip to main content
Share / Export

Managing RP Report Locations

RP Report Locations points Vista to where reports are stored (network path or web address). Form help: About the RP Report Locations Form. Procedures: Set Report Locations and Set Report Locations - VRL. There is no help slug managing-rp-report-locations. The report list and per-report assignment live on RP Report Titles.

Standard Vista reports are grouped by module (each module its own directory), so each module directory usually gets its own location. The same applies to other files/documents launched from a module’s Reports menu. Define a location for each directory or subdirectory when reports sit in multiple places. Each report is assigned to one location on RP Report Titles.

Before you start​

  • Check the deployment method on the Main Menu status bar. It decides which topic applies.
    • VRL on-premises or VRL Cloud: use Set Report Locations - VRL only.
    • Any other deployment: use Set Report Locations (non-VRL); do not use the VRL topic.
  • Red READ ONLY on the form means fields cannot be changed; that switch is in Viewpoint Configuration on the server.
  • SSRS servers are maintained in RP RS Server.

Steps — non-VRL​

  1. Confirm deployment is not VRL on-premises or VRL Cloud.
  2. Location: enter a location name (up to 10 characters). Field defs call it informational; procedures treat it as the name you assign on RP Report Titles.
  3. Location Type: UNC – Network Path (Crystal) or URL – Web Address (SSRS).
  4. Report Path (follow field help):
    • Network: full UNC path, not a mapped drive. Browse is available only on LAN deployment.
    • Web: enter the address.
    • Do not save custom reports under Viewpoint Repository\Reports\Standard (release updates overwrite it). Use Viewpoint Repository\Reports\Custom (optional module or company\module folders). Crystal example: \\servername\Viewpoint Repository\Reports\Custom.
    • SSRS: root path on the SSRS Report Server plus subfolders (example VCS/Custom/BobsReports), not the entire OS path; compare standard RS_Custom. Then set Server Name (F4; F5 opens RP RS Server).
  5. Assign the location on RP Report Titles (one location per report).

Steps — VRL​

  1. Confirm deployment is VRL on-premises or VRL Cloud.
  2. Enter Location, Location Type, and Report Path.
  3. Path rules as published (they conflict for on-premises — see Hard rules):
    • LAN and VRL on-premises: directory must be a subdirectory of the directory on the API Settings tab of Viewpoint Configuration on the app server.
    • VRL Cloud: any entry is valid.
    • VRL on-premises only: any entry is valid.
  4. SSRS: set Server Name (F4).
  5. Assign on RP Report Titles.

Hard rules​

  • Use the topic that matches deployment; the other “does not apply.”
  • One location per directory (including subdirectories) and for non-report items on the Reports menu.
  • UNC only for network paths; no mapped drives (non-VRL / field help). Custom reports must not live in Standard.
  • Field heading is Server Name; procedures often say RS Server Name.
  • VRL on-premises path guidance contradicts itself (must be under API Settings vs “any entry is valid”). Prefer Viewpoint Configuration API Settings when both apply, and confirm for your deployment.

Notes​

  • Related: RP Report Titles; RP RS Server; Viewpoint Configuration; Adding Reports to Module Menus.