topic Re: in line chart x axis scale should always start from -24 irrespective of the data. in App Development

in line chart x axis scale should always start from -24 irrespective of the data.

Qlikbuddy — Tue, 25 Nov 2025 08:41:06 GMT

I am deriving a field in the script called months_until_tld_expire and creating a line chart by count the subs in the measure.

as we know in qlik generally the scale values will come dynamically based on the data. but here user wanted this specific feature like always the scale should start from -24 irrespective of the data. why because their current excels report does the same. so wanted this feature.

scale limit is like -24 to +12 but starting point should always be the -24. if we select 202401 from discount_Start_month then it should start from -24 and ends at nov 2025 (month of today)

if we select 202402, then it should start from -24 and ends at oct 2025. etc.

kindly help how can we achieve this.

Re: in line chart x axis scale should always start from -24 irrespective of the data.

Daniel_Castella — Tue, 25 Nov 2025 12:04:14 GMT

Hi @Qlikbuddy

If I'm not wrong, this cannot be done with the native bar chart. I mean, the offset cannot be moved from 0 to -24, at least in Qlik Sense, maybe in Qlikview it is possible.

However, there is a trick. You can create two measures, one as your expression and the second with -24 - your expression. Then, if you paint it white the segment for the first measure, it seems like you moved the offset. Like in this picture I made on my end:

The bad point is that you cannot colour each bar, all will be the same color.

Let me know if this helps you or if you need further details.

Kind Regards

Daniel

Re: in line chart x axis scale should always start from -24 irrespective of the data.

Qlikbuddy — Tue, 25 Nov 2025 12:30:29 GMT

Hi @Daniel_Castella , thanks for the response.

above excel screenshot i added to show that whatever the selection made it has to start from -24. but the real requirement is to get that in a line chart like below but scale should start from -24 always irrespective of the data/month that we selected. currently 202401 was selected and as per the data its correct scale is starting at -22 and but client specific requirement is like scale should always start from -24.

Re: in line chart x axis scale should always start from -24 irrespective of the data.

Nagaraju_KCS — Tue, 25 Nov 2025 13:05:39 GMT

Try this

Go to the Properties panel for the Line Chart.

Navigate to Appearance.

Expand the X-axis settings.

Ensure Continuous scaling is selected.

Set the Range from Auto to Custom.

Minimum: Input the fixed value: -24

Maximum: Input the dynamic expression: =(Year(Today()) * 12 + Month(Today())) - (Year(Date#(Min(discount_Start_month), 'YYYYMM')) * 12 + Month(Date#(Min(discount_Start_month), 'YYYYMM')))

Re: in line chart x axis scale should always start from -24 irrespective of the data.

marcus_sommer — Tue, 25 Nov 2025 13:10:01 GMT

I think you could create such views by adding appropriate information to the data-model. In this case within the calendar. There could be a field like:

(year(today())*12+month(today()))-(year(MyDate*12+month(MyDate)) as PeriodOffset

which would be alone sufficient as UI dimension if the view should be working against a fixed period - today() might be replace with any other start-date.

If the view needs to be dynamic to a period-selection the above offset could be used within a condition like:

sum({< PeriodOffset = {">=$(=max(PeriodOffset)-24)<=$(=max(PeriodOffset)+12)"}>} MyValue)

which would filter the chart appropriate. If the dimension should be really show -24 to + 12 a similar logic might be applied to a calculated dimension, maybe something like this:

dual(PeriodOffset - $(=max(PeriodOffset), PeriodOffset)

Be aware that you will see only those periods which have appropriate fact-data because missing fact-records respectively NOTHING couldn't be shown even if there are such dimension-values within the calendar. In such cases is it usually the best to populate the missing data within the data-model.

Re: in line chart x axis scale should always start from -24 irrespective of the data.

Qlikbuddy — Tue, 25 Nov 2025 13:40:45 GMT

thanks for the response, but i dont see any such options

Re: in line chart x axis scale should always start from -24 irrespective of the data.

Qlikbuddy — Tue, 25 Nov 2025 13:45:09 GMT

thank you @marcus_sommer for the response.

I am using a teradata query in the back end and there is no master calendar for this actually. the dimension is derived like below.

,(EXTRACT(YEAR FROM TLD_Expiry_Date) - EXTRACT(YEAR FROM CURRENT_DATE)) * 12

+ (EXTRACT(MONTH FROM TLD_Expiry_Date) - EXTRACT(MONTH FROM CURRENT_DATE)) AS Months_Diff_Till_today

and measure is count({<TLD_Flag = {1}>} Distinct subs_id)

Re: in line chart x axis scale should always start from -24 irrespective of the data.

Daniel_Castella — Tue, 25 Nov 2025 13:52:19 GMT

Hi @Qlikbuddy

In this case, I think that it would work better if done in the script, like this code:

TAB:
LOAD
A ,
B
FROM [lib://DataFiles/bar chart.xlsx]
(ooxml, no labels, table is Sheet1);

INL:
NoConcatenate
LOAD Month_Diff, Value
INLINE [
Month_Diff, Value
-24, 0
-23, 0
-22, 0
-21, 0
-20, 0
-19, 0
-18, 0
-17, 0
-16, 0
-15, 0
-14, 0
-13, 0
-12, 0
-11, 0
-10, 0
-9, 0
-8, 0
-7, 0
-6, 0
-5, 0
-4, 0
-3, 0
-2, 0
-1, 0
0, 0
1, 0
2, 0
3, 0
4, 0
5, 0
6, 0
7, 0
8, 0
9, 0
10, 0
11, 0
12, 0
];

Concatenate(TAB)
Load Month_Diff as A, Value as B
RESIDENT INL
where not exists (A,Month_Diff);

Drop table INL;

You simply create an Inline table with the values from -24 to 12 with 0 as value. Then you concatenate them to your data for the month diff that are not existing on your original data.

Then you end with a chart like this (note I used some random values for fields A and B coming from excel):

Obviously, you will have more fields than the ones I used for this simple example, but for me the idea should be this one. Let me know if it works for you.

Kind Regards

Daniel

Re: in line chart x axis scale should always start from -24 irrespective of the data.

Nagaraju_KCS — Tue, 25 Nov 2025 14:02:15 GMT

See this

Re: in line chart x axis scale should always start from -24 irrespective of the data.

Qlikbuddy — Tue, 25 Nov 2025 14:13:47 GMT

thanks again @Daniel_Castella, and this scale should change as per the tld binding filter. its like if the TLD binding is 24/24 then scale should start at -24 to 12.

if its TLD 12/12 then scale should start at -12 to 12

and if by fault we should show it like -36 to 12.

Re: in line chart x axis scale should always start from -24 irrespective of the data.

marcus_sommer — Tue, 25 Nov 2025 14:15:32 GMT

IMO the use of (n) master-calendars is absolutely mandatory - (nearly) each kind of data-set has a date-relation and beside the simple deriving of period-information like year, month and so on all kinds of flags, offset, rolling-periods and and and could be included ... Not only useful within the data-models else within the ETL part to join/map any information.

Very important: it's enough to do this work once for the entire environment - and then picking from there the specific needed fields and periods. Therefore don't waste time to do all the date-related preparation/calculation again and again and in the worst case even within the UI.

How to use - Master-Calendar and Date-Values - Qlik Community - 1495741

Re: in line chart x axis scale should always start from -24 irrespective of the data.

Daniel_Castella — Tue, 25 Nov 2025 14:27:20 GMT

Hi @Qlikbuddy

Well, I would need to have more information about how you create the filter, but I think that if you adjust the dimension like in this picture, you can cut to the wanted value.

For the faulty, if the maximum range needs to be -36, you need to expand the inline table I provided in the script from -24 to -36; and later cut the graph like in the picture above. Note that the value can be set through a variable which value can change based on the filter you commented.

Kind Regards

Daniel

Re: in line chart x axis scale should always start from -24 irrespective of the data.

Qlikbuddy — Tue, 25 Nov 2025 14:34:35 GMT

thanks much @marcus_sommer for sharing your incredible article link. i respect your suggestion for using the master calendar. but here my case is little different with too many date columns. its about discounts related dashboard and there are 3 different types of discounts and each with start, end and expire dates. and main table is Base table which is having another date column.

I have created a master calendar by using the link table approach where I used base table date + and all 3 discounts expiration dates to created a Common_Date.

I kind of never worked with these many dates (3 discount start, 3 discount end, 3 discount expiration and 1 Base closing date) almost 10 dates. and its really messy. can you please show some light on how to combine the dates when we have these many.

currently for 3 discount expiration + 1 Base closing date --- I have created a common_date.

can I do the same for 3 discount start dates as well ?

Re: in line chart x axis scale should always start from -24 irrespective of the data.

marcus_sommer — Tue, 25 Nov 2025 18:51:24 GMT

Having 10 date-fields within the source-data doesn't mean that you need 10 date-fields within the final data-model. Quite probably could the number of fields be reduced - depending of the relationship between the date-fields and the view-requirements you might be ending with a single date-field.

Unfortunately there is no simple rule how to merge them and simplifying the data-model - ideally is a star-scheme with a single fact-table and n surrounding dimension-tables but sometimes it might be sensible not be to restrictive - and maybe keeping some aggregated facts as a dimension-table, too.

If your start/end dates are date-areas it's within the most scenarios helpful to resolve them into dedicated dates with an intervalmatch-logic (or more powerful + flexible with internal load while-loops). Here is the idea beautifully explained: IntervalMatch - Qlik Community - 1464547

Further I think that the 3 different discount-types could be resolved from a horizontal level (= n fields) to a vertical level (= n rows) which means there is then only one date-field + an extra field containing the information which discount-type belonged to it. Such kind of things might be done per: The Crosstable Load - Qlik Community - 1468083.

I would also include all kind of offset-calculations + flagging-stuff (expired, renewed, whatever ...) in these steps.

All these things should be carefully considered before going to use n master-calendar and/or combining them in a canonical way: Canonical Date - Qlik Community - 1463578 because the above provides a native usability while using the n calendars is more complex.