Benchmarks. Benchmark constituents and their weights. A new benchmark code creates the benchmark; a full file replaces the constituents of the benchmarks it names. Key: benchmark + symbol. One file: the header attributes, then the records. The business date the data is for (YYYY-MM-DD). Your firm code, shown on Data › Feeds (e.g. F00012). Who produced the file (vendor or system name). When the file was produced (UTC). The number of record elements. A file whose count does not match is refused (F004): it was probably cut short. delta: only the records in the file change, and action="delete" removes one. full: the file is complete; records it does not list are inactivated, up to the feed's safety threshold. One benchmarks record. Elements may appear in any order. The benchmark code. Part of the key. A code: letters, digits, "_", "." or "-", up to 20. Part of the key. The constituent. Part of the key. A ticker symbol: letters, digits, "." or "-", up to 12. Part of the key. Weight in percent. A decimal number written as text, e.g. 1234.5 (min 0 max 100). The benchmark's name (used when it is created). Text, up to 120 characters. User-defined fields (format 1.1). Each <udf> names its slot (1 to 10) and optionally the field's name; the value is checked against the type your Admin gave the field. A slot that is not active for your firm is refused (U101), a value of the wrong type too (U102), and a name that differs from the slot's name (U103). upsert (insert or update by key) or delete (removes the record; a security or account is inactivated, never deleted). One user-defined field value (at most 255 characters). The slot, 1 to 10 (the column udf_1 .. udf_10). The field's name as set up by your Admin (checked when given).