Qlik Community

New to Qlik Sense

Discussion board where members can get started with Qlik Sense.

Not applicable

Display AS xdisplay

On the Enterprise version of Qlik Sense I am doing a direct connect and wanting to change the column headings.  I know in the 2.2.4 version of the desktop you can do it as first pic below correct?  I can load with only one synthetic key error before this change.

We have not ipgraded to the newest version of Enterprise yet, is this my problem?

.

LIB CONNECT TO 'pmd-sandbox (pharmore_rwinkel)';

LOAD FacId,
    RxNo,
    DispenseDt as OEDDispenseDt,
    PatId AS OEDPatId,
    TransType AS OEDTransType,
    ProfileOnly AS OEDTransType,
    PhrNPI AS OEDPhrNPI,
    InitReview AS OEDInitReview,
    EnteredByNPI AS OEDEnteredByNPI,
    Entered AS OEDEntered,
    Deleted AS OEDDeleted;
SQL SELECT FacId,
    RxNo,
    DispenseDt as OEDDispenseDt,
    PatId AS OEDPatId,
    TransType AS OEDTransType,
    ProfileOnly AS OEDTransType,
    PhrNPI AS OEDPhrNPI,
    InitReview AS OEDInitReview,
    EnteredByNPI AS OEDEnteredByNPI,
    Entered AS OEDEntered,
    Deleted AS OEDDeletedLOAD FacId
  
FROM Rx.dbo.OrderEntryStats;

LIB CONNECT TO 'pmd-sandbox (pharmore_rwinkel)';

THE BEFORE

   LIB CONNECT TO 'pmd-sandbox (pharmore_rwinkel)';

LOAD FacId,
    RxNo,
    DispenseDt,
    PatId,
    TransType,
    ProfileOnly,
    PhrNPI,
    InitReview,
    EnteredByNPI,
    Entered,
    Deleted;
SQL SELECT FacId,
    RxNo,
    DispenseDt,
    PatId,
    TransType,
    ProfileOnly,
    PhrNPI,
    InitReview,
    EnteredByNPI,
    Entered,
    Deleted
FROM Rx.dbo.OrderEntryStats;

1 Solution

Accepted Solutions

Re: Display AS xdisplay

Ah, no. You already renamed the fields in the sql statement. So the preceding load can only 'see' the new names.

LIB CONNECT TO 'pmd-sandbox (pharmore_rwinkel)';

LOAD FacId,
    RxNo,
     OEDDispenseDt,
     OEDPatId,
     OEDTransType,
     OEDTransType,
     OEDPhrNPI,
     OEDInitReview,
     OEDEnteredByNPI,
     OEDEntered,
     OEDDeleted;
SQL SELECT FacId,
    RxNo,
    DispenseDt as OEDDispenseDt,
    PatId AS OEDPatId,
    TransType AS OEDTransType,
    ProfileOnly AS OEDTransType,
    PhrNPI AS OEDPhrNPI,
    InitReview AS OEDInitReview,
    EnteredByNPI AS OEDEnteredByNPI,
    Entered AS OEDEntered,
    Deleted AS OEDDeletedLOAD FacId
  
FROM Rx.dbo.OrderEntryStats;

Or just leave out the preceding load completely. If you're only renaming fields you don't need it.

LIB CONNECT TO 'pmd-sandbox (pharmore_rwinkel)';

SQL SELECT FacId,
    RxNo,
    DispenseDt as OEDDispenseDt,
    PatId AS OEDPatId,
    TransType AS OEDTransType,
    ProfileOnly AS OEDTransType,
    PhrNPI AS OEDPhrNPI,
    InitReview AS OEDInitReview,
    EnteredByNPI AS OEDEnteredByNPI,
    Entered AS OEDEntered,
    Deleted AS OEDDeletedLOAD FacId
  
FROM Rx.dbo.OrderEntryStats;


talk is cheap, supply exceeds demand
4 Replies

Re: Display AS xdisplay

On the Enterprise version of Qlik Sense I am doing a direct connect and wanting to change the column headings.

What do you mean with 'direct connect'?

I know in the 2.2.4 version of the desktop you can do it as first pic below correct?

Which picture? I don't see any pictures in your post.

I can load with only one synthetic key error before this change.

Which change? What has changed where?

We have not ipgraded to the newest version of Enterprise yet, is this my problem?

No, the version of Qlik Sense is irrelevant.


talk is cheap, supply exceeds demand
Not applicable

Re: Display AS xdisplay

This does not work

LIB CONNECT TO 'pmd-sandbox (pharmore_rwinkel)';

LOAD FacId,
    RxNo,
    DispenseDt as OEDDispenseDt,
    PatId AS OEDPatId,
    TransType AS OEDTransType,
    ProfileOnly AS OEDTransType,
    PhrNPI AS OEDPhrNPI,
    InitReview AS OEDInitReview,
    EnteredByNPI AS OEDEnteredByNPI,
    Entered AS OEDEntered,
    Deleted AS OEDDeleted;
SQL SELECT FacId,
    RxNo,
    DispenseDt as OEDDispenseDt,
    PatId AS OEDPatId,
    TransType AS OEDTransType,
    ProfileOnly AS OEDTransType,
    PhrNPI AS OEDPhrNPI,
    InitReview AS OEDInitReview,
    EnteredByNPI AS OEDEnteredByNPI,
    Entered AS OEDEntered,
    Deleted AS OEDDeletedLOAD FacId
  
FROM Rx.dbo.OrderEntryStats;

Re: Display AS xdisplay

Ah, no. You already renamed the fields in the sql statement. So the preceding load can only 'see' the new names.

LIB CONNECT TO 'pmd-sandbox (pharmore_rwinkel)';

LOAD FacId,
    RxNo,
     OEDDispenseDt,
     OEDPatId,
     OEDTransType,
     OEDTransType,
     OEDPhrNPI,
     OEDInitReview,
     OEDEnteredByNPI,
     OEDEntered,
     OEDDeleted;
SQL SELECT FacId,
    RxNo,
    DispenseDt as OEDDispenseDt,
    PatId AS OEDPatId,
    TransType AS OEDTransType,
    ProfileOnly AS OEDTransType,
    PhrNPI AS OEDPhrNPI,
    InitReview AS OEDInitReview,
    EnteredByNPI AS OEDEnteredByNPI,
    Entered AS OEDEntered,
    Deleted AS OEDDeletedLOAD FacId
  
FROM Rx.dbo.OrderEntryStats;

Or just leave out the preceding load completely. If you're only renaming fields you don't need it.

LIB CONNECT TO 'pmd-sandbox (pharmore_rwinkel)';

SQL SELECT FacId,
    RxNo,
    DispenseDt as OEDDispenseDt,
    PatId AS OEDPatId,
    TransType AS OEDTransType,
    ProfileOnly AS OEDTransType,
    PhrNPI AS OEDPhrNPI,
    InitReview AS OEDInitReview,
    EnteredByNPI AS OEDEnteredByNPI,
    Entered AS OEDEntered,
    Deleted AS OEDDeletedLOAD FacId
  
FROM Rx.dbo.OrderEntryStats;


talk is cheap, supply exceeds demand
Not applicable

Re: Display AS xdisplay

Community Browser