From time to time, it is necessary to output the data from the same field in the same record, multiple times. The method Freedombase uses to point at the next record would normally prevent this; the moment Freedombase sees the same field name referenced again, it will point at the next record.

This 'point at the next record' behaviour can be prevented, however, by appending a 'C'urrent tag to the end of the Attribute tag, in the format %System_Class_Attribute_C%. Wherever Freedombase sees the 'C'urrent flag, it output the data without moving the pointer.

For example, if the page contained the following tags:

%EXAMPLES_CUSTOMER_NAME%
%EXAMPLES_CUSTOMER_ADDRESS_C%
%EXAMPLES_CUSTOMER_NAME_C%
%EXAMPLES_CUSTOMER_ADDRESS_C%

The following would occur (please see the explanation in brackets):

%EXAMPLES_CUSTOMER_NAME% (NAME has not yet been output for the current CUSTOMER record, so output the value of the NAME field from the current CUSTOMER record.)
%EXAMPLES_CUSTOMER_ADDRESS_C% (Output the value of ADDRESS from the Current record. Do not check if the pointer should be moved, and do not move the pointer.)
%EXAMPLES_CUSTOMER_NAME_C% (Output the value of NAME from the Current record. Do not check if the pointer should be moved, and do not move the pointer.)
%EXAMPLES_CUSTOMER_ADDRESS_C% (Output the value of ADDRESS from the Current record. Do not check if the pointer should be moved, and do not move the pointer.)

It is actually more efficient to use the 'C'urrent option wherever possible, and to only use the Attribute tag without the 'C'urrent option, when Freedombase needs to check, set and possibly move the pointer. Most default pages within Freedombase will set the 'C'urrent option on all but one or two Attribute tags, in order to take advantage of this efficiency gain.