Description

 This page provides the solution for the issue of missing links between VB.Net constant field and stored procedures.

Observed in CAST AIP
Release
Yes/No
8.3.x(tick)
8.2.x(tick)
8.1.x(tick)
8.0.x(tick)
7.3.x(tick)
Observed on RDBMS
RDBMS
Yes/No
Oracle Server(tick)
Microsoft SQL Server(tick)
CSS3(tick)
CSS2(tick)
Step by Step Scenario

Below is the step-by-step scenario leading to the problem:

  1. Run analysis.
  2. Check in enlighten for missing links between constant field and stored procedures.
Impact of the Problem

The impact of the problem on the analysis or the dashboard is: Missing links are found between VB.Net constant field and stored procedures

Action Plan

As an example : In this case, the constant field is assigned the value of stored procedure's name.

Here PC_COMMERCIAL_ACCOUNT_SELECT is assigned a value "pc_ecm_commercial_account_s " which is actually a stored procedure name.

To fix this issue:

  1. Deactivate the option "Create accurate client/server links" for dataflow. This is used by the dataflow to build SQL string. This option is production option/.Net/Dynamic Analysis Option. If you deactivate this option, the principal impact is on DLM. All Client/Server links are in DLM.
  2. You can create a Reference Finder to create links
Impact of the Solution

Impact of the solution on the analysis or the dashboard is: Links will be seen in Enlighten after applying the workaround

Notes/comments

 Ticket # 6281

This solution is applicable for all the SQL objects

Related Pages