Return to main navigation Page
The single-page administration includes spreadsheet-like user interface with easy editing capabilities, powerful search features that allow searches within a single table or across all tables, and enhanced performance and indexing.
|Total Columns in a Table||100 Columns (255 String, 9 Integer, 16 Float)|
|Total Rows in a Table||1,000,000 + Rows|
|String Characters in a Cell||256 Characters|
|Integer Characters in a Cell||16 Characters|
|Float Characters in a Cell||9 Characters|
Unique (case insensitive)
Must look like variable names:
Unique within the Table (case insensitive)
Must look like variable names:
Invalid keywords for Table and Column Names
Many of these keywords are used in BML. They cannot be used in Table or column names.
Data Table Storage
Data Tables are used to store product and commerce data. They can be accessed from any part of the CPQ Cloud application where BML is used. The purpose of storing complex business logic in Data Tables is for ease of maintenance.
|Data Stored in Excel (CSV)||Data Stored in CPQ Cloud|
Data Table Indexing
Data table indexing is supported for single column indices on individual tables. Indexing a column has the same effect as putting a standard index on a database column: it will create a sorted list of that column for faster access to the data.
How a data table should be indexed depends upon how it is used. An admin should examine the use cases of BMQL access to the Data Tables to see which columns are used for filtering (which appear in the WHERE clause). These are the columns that are candidates for indexing.
For these indexing candidates, the next step is to
examine the selectivity that each column offers. For instance, if a
column has a
yes or a
no value, that is not a
selective column since choosing a value will eliminate only half of the
table. A column with a unique ID for each record, however, would be
highly selective as it will narrow down a search to exactly one record.
Indexes will not work with fuzzy operators. That is, finding all rows with a column containing the letter E will not benefit from indexing that column.
Indexing and Queries
The best use of an index is when it is used with a well thought-out query plan. For each query that is run on the Data Table, for best performance, only the most selective column should be indexed.
When adding indices to queries, it is important to recognize the relative impact that an index will have.
The best candidate for indexing is a large Data Table with a selective column that is queried frequently.
Indexes cannot compensate for poorly designed queries. A query with a dozen conditions in the WHERE clause will only see a small benefit from an index unless one of the indexes is very selective; this is generally not the case with large filter criteria.
When migrating Configuration or Commerce, a list of dependent Data Tables is displayed in a pop-up window. If these Data Tables are not selected, migration will fail. This pop-up will only appear when menu attribute validations are mapped to a Data Table, but not when the Data Table is used in BMQL rules.
CPQ Cloud has included Natural Keys within Data Tables to improve efficiency. As a result of Natural Keys, the bulk upload files that modify Data Table data now only require the table records that are to be changed. Natural Key can be a single column or a combination of several columns that produce a unique identifier for each record (row). The creation of these Natural Keys reduces the maintenance downtime of Data Tables by including only Data Table changes upon upload. Users no longer need to purge and reload all Data Table rows to edit a subset of rows.
Accessing Data Tables
Information in Data Tables can be accessed from anywhere in your CPQ Cloud application that uses advanced functions.
To access and manage Data Tables
Click Admin to go to the Admin Home Page.
Click Data Tables in the Developer Tools section.
The Data Table Administration page appears.
From this page, you can add tables and folders, import and export table files, and perform searches across tables.
If an offline back-up is still needed
Log a case requesting a retrieval of information as of XX date/time.
CPQ Cloud only creates back-ups of the entire site. If you require specific Data Table(s) back-ups, you must do so yourself.
The first column of a Data Table can be populated with an empty string. A row with data must follow.