Failed to start BASE24 configuration. Does not recognize TOTAL field combined with TERMLN

[Jerry]

Failed to start BASE24 configuration

Enable key field is not a record key field - TOTAL
ITEM: ENABLE KEY(Base24TransactionSummary,TERMLN+TOTAL)
CAUSE: The enable key field is not a key field of the record Base24TransactionSummary.
ACTION: Program continues. No data available.

====================================================

Failed to start BASE24 configuration

Enable key field is not a record key field - TOTAL
ITEM: ENABLE KEY(Base24TransactionSummary,TOTAL+TERMLN)
CAUSE: The enable key field is not a key field of the record Base24TransactionSummary.
ACTION: Program continues. No data available.

[ChristopherS]

@Jerry

TOTAL is a reserved key and cannot be combined as all of the detail fields are empty like TERMLN and just the categorical fields.

When you use a categorical field the same statistics fields as with TOTAL are utilized.  So if you are just looking for by Logical Network Summary (LNET) you get that with simply TERMLN key but the TOTAL switch swide summary is a completely seperate key.

IF you are trying to put the Switch Total with individual TERMLN breakdown in the same display/dashboard window, you cannot do it in a table..but can in one of the charting options by simply adding the same record twice and then using a different associate record on each line.

Something like this:

[Jerry · Accepted solution]

Hi Chris;

Using an ALL where clause with a top 10 limit; I tried using the TERMLN asociate with the TOTAL and TERMLN field but it did not present ant data.

I ended up using the B24NODE asociate name with only the ACQUIRERFIID, TOTAL and B24NODE in order to get the sum of all transaction from each Logical Network.

Here is the results using the top 20 limit: 

[ChristopherS · Accepted solution]

@Jerry

I might be missing something you are trying to do.. but from the output you should absolutely be able to do that with a single level Associate Name/Key without having to do any combines to get by TERMLNET or CARDLNET or by Systemname in Base24..  I've done it many times on many customer systems.

When you utilize keys that are non-specific or try to utilize multiple keys in a tabular view you also can get some odd results as they are meant for 1 Associate record really... but yes as you realized technically you can but except in a database it is generally not best practice to do so in one record view as well you may see it is excessively load burying view compared to other views with less rows of data (using PVIEWS).   

A single associate key not working may be due to verys light subtlies when you defined the key, on the wrong record, or case sensitivity differences between the way it is in the Base24 conf and how you entered it in the display. 

You will never need (nor will it work) adding TOTAL reserved keyword with any other keyword/associate name.. all others can be combined. 

Feel free to drop me an email with some more detail if you like. 

Christopher