Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
ttmaroney
Contributor III
Contributor III

Please help with set analysis around dates I am loading.

I am loading in service tickets with:

[Open Date], [Priority] and [Affected Software].

I am also loading a spreadsheet on go-lives (when systems were added or changed) with:

[Go Live Name],

[Affected Software],

[DNeg90] (The date 90 days before the go-live),

[D0] (Go live date),

[D14] (Date two weeks after go live), and

[D90] (Date 90 days after the go-live).

 

I want to make a table with go-live name, affected software, and how many service tickets surround that go-live date as follows:

  • 90 days prior
  • First 14 days
  • First 90 Days
  • Prior to go-live date
  • Since go-live date

I have read many posts and tried like 20 ways, all which failed. Can someone please tell me what I am going wrong?

 

90 days prior

Tried: =count( {$<[Open Date]={">=$(=Date(D0,'YYYY-MM-DD')"}>}Priority

 

First 14 days

Tried: =count({<[Resolve Date]= {">=$(=min(D0))<=$(=max(D14))"}> } Priority)

 

First 90 Days

Tried: =count({<[Resolve Date]= {">=$(=min(D0))<=$(=max(D90))"}> } Priority)

 

Prior to go-live date

Tried: =Count({<[Resolve Date]={"<=$(=D0)"}>} Priority)

 

Since go-live date

Tried::   =count( {$<[Open Date]={">=$(=Date(D0,'YYYY-MM-DD')"}>}Priority

 

   

System - Go LiveAffected SoftwareDNeg90D0D14D90All TicketsPrior 90
Go live Name 9Application711/29/20172/27/20183/13/20185/28/201820-
Go live Name 1 Version 2Application19/20/201712/19/20171/2/20183/19/201826-
Go live Name 15Application109/17/201712/16/201712/30/20173/16/2018454-
Go live Name 12 group EApplication99/6/201712/5/201712/19/20173/5/2018152-
Go live Name 12 group DApplication97/12/201710/10/201710/24/20171/8/2018152-
Go live Name 12 group CApplication96/14/20179/12/20179/26/201712/11/2017152-
Go live Name 3Application25/27/20178/25/20179/8/201711/23/20173054-
Go live Name 12 group BApplication95/10/20178/8/20178/22/201711/6/2017152-
Go live Name 12 group AApplication94/12/20177/11/20177/25/201710/9/2017152-
Go live Name 7Application53/31/20176/29/20177/13/20179/27/201745-
Go live Name 1 Version 1Application13/29/20176/27/20177/11/20179/25/201726-
Go live Name 14Application93/15/20176/13/20176/27/20179/11/2017152-
Go live Name 13Application92/15/20175/16/20175/30/20178/14/2017152-
Go live Name 6Application41/29/20174/29/20175/13/20177/28/20176765-
Go live Name 10Application81/24/20174/24/20175/8/20177/23/2017158-
Go live Name 2Application21/7/20174/7/20174/21/20177/6/20173054-
Go live Name 5Application312/31/20163/31/20174/14/20176/29/20171-
Go live Name 4Application211/2/20161/31/20172/14/20175/1/20173054-
Go live Name 11Application89/16/201612/15/201612/29/20163/15/2017158-
Go live Name 8Application67/19/201610/17/201610/31/20161/15/201713174-

 

10 Replies
ttmaroney
Contributor III
Contributor III
Author

Digvijay,

I'm sure your answer was right, and there must be some sort of issue in my model or formatting. This is only something I needed to run once, and since then a coworker was able to easily do it in another tool, which will remain nameless. I'm sure we could get to the bottom of it, but right now, it's not worth the calories since we have our answer.  Thanks for the help.