Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser 4 > Collecting, transforming, and publishing > ETL workbooks > Publishing data to a schema

Publishing data to a schema

Table of contents
No headers

This article is part of To collect, transform, and publish data:

4. Configure publishing

Publishing data to a schema is the act of creating a record in the Cloud Cruiser database for each row in a worksheet. This provides two benefits:

  • Makes this IT usage data available to Cloud Cruiser Insights modules, which use this database as their data source.
  • Triggers the Charge engine to run, which matches these rows against the services you have defined and creates charge records in the Cloud Cruiser database for them. This is the financial information, available both in standard reports and Insights modules, that you use to bill your customers.

Publishing data to a schema is different from publishing configuration data, such as customers or services.

To publish a worksheet to a schema

  1. From the Sheet tab in the ribbon, choose Publish Data and the schema that you want to publish to, as shown in the following screenshot.

    Screenshot of the ribbon with Publish Data > To Virtual Machine Schema selected

    The Publish dialog box appears.
    ​If you need to create any analytics reports using this schema, note the Analytics name in italics so that you will recognize the schema when creating a data source in HPE Consumption Analytics Portal Desktop.
  2. If an Account ID table exists, map worksheet columns to your account levels.
    When this table exists, the schema requires each row to include an account ID to associate usage with a customer. Your mappings here determine which column in the worksheet provides the value for each level in an account ID. Because account IDs are hierarchical, the following requirements apply:
    • You must map the first account level to a column. This is indicated by the icon Checkbox icon indicating that the first account level is required.
    • If you map any level below the first one, all account levels above it must also be mapped. This is indicated by the icon Arrow icon indicating that an account level is required because a lower level is mapped.
    • -none- option is available for rare cases where you don't have an appropriate column to map to a required level. You cannot use -none- for all account levels.

    In addition to selecting from a list of columns found in the sample data in the worksheet, you can manually enter the name of another column, or enter a literal value to be used in all rows by enclosing it in double quotes (").

    This also applies to the Schema Fields table.

  3. In the Schema Fields table, map worksheet columns to the fields of the schema.
    Your mappings here determine which column in the worksheet provides the value for each field in the schema.In the Schema Fields table, mapping to each schema field is optional except for the following:
    • Key dimensions. These are the dimensions that combine to uniquely identify an object in a schema record, such as a VM, and are indicated by the icon Key icon indicating that the field is a key dimension and therefore required.
    • Other fields required by the schema. These are indicated by the icon Checkbox icon indicating that the first account level is required.

    If the schema doesn't have appropriate fields for every worksheet column you want to publish, click Edit Schema in the lower left corner to edit the schema definition. For more information, see Managing schemas.

  4. At the top of the Publish dialog box, set other options for the Publish step.
    • Fail When Empty: Whether to cause the flow containing this step to fail when the step does not publish at least one row.
    • Exception Limit: The maximum number of processing exceptions this step can generate without causing the flow containing it to fail.
    • Active: Whether to include this step when running the flow that contains it. Use this option to temporarily deactivate this step during debugging.
    • Auto Generate Fields: Whether to add a field to the schema at run time if the dataset being published contains a column that is not already mapped to a schema field. Use this option to publish columns that might be added to the worksheet in the future.
  5. If you want to publish only certain rows from a dataset, go to the Advanced tab and enter a Filter Condition.
    ​This works the same as a condition applied to a transformation processor. Rows for which the condition is true are published and rows for which it is false are not published.
  6. If you want to change the accounting date of the published data, go to the Advanced tab and change the setting for Accounting Date.
    By default Cloud Cruiser applies the select date as the accounting date, but you can instead opt to apply the date in the End Time column of the first row in the dataset.​
  7. If you want to document the design of this Publish step, go to the Advanced tab and enter text in the Comments field.
  8. Click OK to close the dialog box and apply your changes.
    You must still save the workbook to permanently save this Publish step.

What to do next

To collect, transform, and publish data:

Last modified


This page has no custom tags.


This page has no classifications.

 (c) Copyright 2017-2020 Hewlett Packard Enterprise Development LP