This page provides the solution for the issue of missing links between VB.Net constant field and stored procedures.
Release | Yes/No |
---|---|
8.3.x | |
8.2.x | |
8.1.x | |
8.0.x | |
7.3.x |
RDBMS | Yes/No |
---|---|
Oracle Server | |
Microsoft SQL Server | |
CSS3 | |
CSS2 |
Below is the step-by-step scenario leading to the problem:
- Run analysis.
- Check in enlighten for missing links between constant field and stored procedures.
The impact of the problem on the analysis or the dashboard is: Missing links are found between VB.Net constant field and stored procedures
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:
- 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.
- You can create a Reference Finder to create links
Impact of the solution on the analysis or the dashboard is: Links will be seen in Enlighten after applying the workaround
Ticket # 6281
This solution is applicable for all the SQL objects