I need to apply multiple buckets to my financials?

[toucangulyayu]

Hi guys

I often at my job making need to have many segments applied to financial data.  This create buckets, information that place the entries to match the values in the table. 

Often times we need to make brackets of income, and there are multiple applications of these brackets in many spots in our data.

How can i do this to bracket our infomration by financial limits?

Any help would be appreciated.  This Qlik stuff is swell!

[evan_kurowski]

Hello Khom,

Not certain, but... I may have something helpful and useful for your situation.... 

[toucangulyayu]

Thank you Evan, that would be helpful.

[evan_kurowski · Accepted solution]

This repeatable bucketing system I like to use, lets me just set up definitions for as many asymmetrical range buckets as I need (and I keep these around for reusability).  During scripting it loads each definition set, creates the segment boundaries, applies the interval matches against my designated fact fields, and then joins the result field back on to my main fact table.  Has made segmentation somewhat repeatable for my needs.  Hope it helps.

(here's a look at some sample output, 3 pre-defined buckets applied against 2 financial account level encapsulating fields)

[toucangulyayu]

Oh Hey nyeat Eyan.  Dev time for setting up bucket after 1 first will be the much easier now.  I have question, what is large number i see at the "=END" place in buckets table?  something like 9.807####e+15 ???? 

[evan_kurowski]

Well the intervalmatches need an endpoint, in order to complete the bucket (so had to have the >= value & <= value, solely the >= value was not enough)

For top end buckets, since a value was required, needed the best approximation of greater than, and for a 64-bit QlikView implementation, it appears to use 53-bits for the value of the number (the remaining bits reserved for encoding sign, scale, etc..).  That upper end number is the largest number I could form in Qlik that was still treated as a numeric value (and testing values above this point have treated larger values as text).  So it is attempting the Qlik upper limit of numeric value to cap the top bucket.

[toucangulyayu]

I like it, working well for me.  Going to use this.  ty