Jump to content

How to produce the columns without adding dummy column in edited sql in Information Link


Enkeled Kanaj

Recommended Posts

Hi,

 

In the Information Link I have to do custom query where it can not produce the column without adding some dummy column which have to be in order corresponding to the order of the edited sql query.

Is any simple way to get the columns queried inside the edited script without adding this dummy column?

 

image.png.c18ad0ea6506bf4def59af987ab4d084.png

SELECT
    D1."DATE_ID" AS "DATE",
    D1."ERBS" AS "ERBS",
    D1."EUtranCellFDD" AS "EUTRANCELLFDD",
    SUM(CASE D1."DCVECTOR_INDEX" 
        WHEN 1 THEN D1."pmErabEstabSuccAddedQci" 
        ELSE 0 
    END) AS "pmErabEstabSuccAddedQci_1",
    SUM(CASE D1."DCVECTOR_INDEX" 
        WHEN 1 THEN D1."pmErabEstabSuccInitQci" 
        ELSE 0 
    END) AS "pmErabEstabSuccInitQci_1",
    SUM(CASE D1."DCVECTOR_INDEX" 
        WHEN 1 THEN D1."pmErabRelNormalEnbUserInactivityQci" 
        ELSE 0 
    END) AS "pmErabRelNormalEnbUserInactivityQci_1",
    SUM(CASE D1."DCVECTOR_INDEX" 
        WHEN 1 THEN D1."pmErabEstabAttInitQci" 
        ELSE 0 
    END) AS "pmErabEstabAttInitQci_1",
    SUM(CASE D1."DCVECTOR_INDEX" 
        WHEN 1 THEN D1."pmErabEstabAttAddedQci" 
        ELSE 0 
    END) AS "pmErabEstabAttAddedQci_1",
    SUM(CASE D1."DCVECTOR_INDEX" 
        WHEN 1 THEN D1."pmErabEstabAttAddedHoOngoingQci" 
        ELSE 0 
    END) AS "pmErabEstabAttAddedHoOngoingQci_1",
    SUM(CASE D1."DCVECTOR_INDEX" 
        WHEN 1 THEN D1."pmRrcConnReestSuccQci" 
        ELSE 0 
    END) AS "pmRrcConnReestSuccQci_1",
    SUM(CASE D1."DCVECTOR_INDEX" 
        WHEN 1 THEN D1."pmRrcConnReestAttQci" 
        ELSE 0 
    END) AS "pmRrcConnReestAttQci_1"
FROM 
    "DC_E_ERBS_EUTRANCELLFDD_V_RAW" D1
WHERE 
    <conditions>
GROUP BY
    D1."DATE_ID",
    D1."ERBS",
    D1."EUtranCellFDD";

Link to comment
Share on other sites

Hi Enkeled;
Unlike the data connectors, the information links do not have that "Verify" button that generates the columns from SQL. statements.  By design, an information link needs columns  elements definition (as proper objects) to map to the SQL.
The purpose of manually editing SQL was not to reverse engineering to create the necessary column elements but to adapt the generated SQL. This is a paradigm change compared to what you know as "Fee-Hand" SQL in other platforms.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...