Datasets
Datasets are the building blocks of every allocation rule. They hold the business data OneLens needs to share cost out: who or what receives cost, how your business maps to cloud resources, and the usage numbers that decide each share.
Go to Observe → Unit Economics → Datasets.

Dataset types
Click Add to create one of three types.

Entity
A list of records, such as customers, products or business units. An entity is either a Cost Target, which receives allocated cost and becomes the rows of your report, or a Cost Source, which is a dimension used in allocation rules
Your customer list
Mapping
Defines how two sets of records relate
Which cloud accounts belong to which customer
Metric
A numeric time series keyed by an entity, a cost center or a virtual tag
Database size per customer per month
The datasets list
Dataset Name
The dataset's name
Type
Metric, Mapping, or Entity with its role, such as Entity Target
Granularity
How often data is expected, such as Monthly
Input
Manual if people enter the data in OneLens, or Automated if it arrives by API or from a system
Records
Number of records in the dataset
Owner
Who is responsible for the data
Health
Whether data has arrived on time. Stale means no data arrived by the expected date
Created By, Updated By, Last Updated At
Who created and last changed the dataset, and when
Actions
Edit the dataset, or open more options
Add an entity

Click Add → Entity.
Enter an Entity Name. OneLens fills in the Entity ID from it.
Choose a Role:
Cost Target if this entity should receive allocated cost and appear as rows in the report, such as customers.
Cost Source if it is a dimension used in allocation rules.
Pick an Owner and add a Description.
Under Data Setup, choose the Data Granularity and the Input Method: Manual (UI input) or Automated (API/System).
For automated data, set Expect data by. If no data arrives by that day, OneLens marks the dataset as stale. For example, with Monthly and the 5th, the dataset is flagged stale if no data is detected by the 5th of the month.
Add a mapping
A mapping links records on one side to records on the other. The "from" side can be a Cost360 Dimension, such as cloud account, or one of your entities. The "to" side is usually one of your entities. For example, you can map cloud accounts to customers.

Click Add → Mapping.
Enter a Mapping Name and choose the Cardinality, such as Many:Many.
Choose the From Entity Type and From Entity, then the To Entity Type and To Entity.
Pick an Owner.
Under Data Setup, choose the Data Granularity and Input Method.
For manual input, set up the monthly data reminder. Choose who to email and on which day of the month. OneLens sends the reminder only if no data has been submitted by then.
Manual values show as editable cells in the output report, and OneLens keeps a version history of each entry.
Add a metric
A metric needs at least one numeric field. OneLens adds that numeric field for you, and it cannot be removed.

In step 2, Set-up metric fields, define each field:
Data Field
The field name in your data
Field Type
What the field holds: an entity key (such as a customer), a Number, or the Usage Date
Rename As
The name to show in reports
Unit
The unit for numbers, such as GB
Required?
Whether every record must have a value
Click Download Template to get a file with these fields, so you can upload initial records.
Last updated

