The first step in onboarding data is to create custom fields. You and your organization will be using those to enter the data.
To add datapoints, you have a few options. You can:
- upload an Excel file,
- insert them on Dashboard Price Monitor, or
- provide from the Sentieo Connect Portal.
Create and Manage Fields
To create and manage fields, head to the Overview section of the Sentieo Connect portal. You can find it in the Add Tab menu of the Sentieo tab bar.
Sentieo Connect Portal Overview
The overview page serves two purposes:
- Review a list of all the fields already in the system, and
- Create, amend or delete new ones.
Create a new field
To create a new field, press the “Create Field” button.
Some fields are required.
- Field Name: The name you want to give the field.
- Excel Code: The Excel code you want to give the field. As you start typing a field name, Sentieo will suggest a field code automatically but you can change to a desired name. Field codes are unique for every organization, and once a field is created, it cannot be changed.
- Content Type: A field needs a content type. It will determine what kind of data can go in it and what can be done with it.
For example, a field defined as “Numeric” will accept only numbers; on Screener, this will allow you to be able to filter for values equal or greater to a certain value, and so forth.
On the other hand, a field that is a periodic text will only accept values that are text, but also requires you to provide a period (eg: FY2020) along with the field.
Sentieo offers a handful of generic content types (Numeric, Boolean, Text, List, Dates), as well as many pre-built content types (Eg: Revenue estimate, Price Target, or Analyst Name).
Why use pre-built content types? We recommend using pre-built content types because, besides the nature of data, they also pre-set other important parameters for you, such as the periodicity, the currency, or the lookback period. At a later date, we will be delivering new features leveraging user and Sentieo data that will take advantage of user fields being tagged to concepts like these.
For example, soon we will introduce the ability to generate an LTM series out of quarterly data. If this data is from the income statement, it will not be treated the same way it would be from a balance sheet (sum of periods vs average of periods).
We are working on many more full-scale features which benefit from the proper usage of content type, so we highly encourage you to try and use them as much as possible.
The full list of pre-built content types is available here .
- Periodicity (Default = No): A periodic field lets you store data which is periodic by nature and follow the financial statement reporting schedule of a company (eg: Revenue or EPS estimates). Typically, you shouldn’t create separate fields for Revenue FY2020 and Revenue FY2021; create only one field and set Periodicity to “Yes”. Most key financial model metrics are already covered with pre-built content types and are all marked as periodic.
You can also customize the following items, they are either optional or come pre-populated with default values:
- Units (Default = Unit): Chose the unit in which you will be uploading the data. For example, if you select “Trillions”, and you upload 4.32, Sentieo Connect will understand that you meant 4.32 trillion and not 4.32 units. This is useful later on when displaying data on Screener or Price monitor, or when applying formulas with custom expressions or hybrid series in Plotter.
- Description: Provide a quick summary of what the field is intended to display. This will be shown in various menus across Sentieo, including the field picker on Price Monitor or Screener. It also provides context for your team to understand what the field is meant for.
- Advanced options: Some items are either optional or pre-configured and hidden in the Advanced Options section.
Click “Show Advanced Options” to show them and make changes
- Header Label (Default = same as Field name): This is the name shown when the field is displayed in tables on Sentieo and in Excel. If left empty, the Field Name will be used in table headers
- Default Data Source: Each datapoint is tagged with a source. When you create a field, you can define a default source for the datapoints you are going to load in the field. Whenever a datapoint is created without specifying the source, the default data source is applied to it. Data source is added informatively in subscript to tables on Notebook Notes that contain Sentieo Connect data.
- Lookback (Default = infinite): We define lookback as the maximum period of time a datapoint is still considered “fresh” and valid. It is by default set to “infinite”, but it is probably good practice for you to reduce it to a reasonable cut-off time, for example 30 days.
To illustrate this, if you set Lookback to 30 days, and you ask Screener or Excel to fetch the field “MyRevenueEstimate” as of today, but the latest value is older than 30 days, it will not return anything. Lookbacks help you make sure you do not rely on stale or outdated data.
- Currency (Default = No Currency): Defines what the data’s currency type the is. At the moment, you can pick between “No Currency”, “Trading Currency” and “Reporting Currency”. Setting the correct currency helps provide better automatic results across the various tools in Sentieo.
- Adjustments (Default = disabled; only some pre-built fields): We offer you the ability to automatically reflect corporate and capital actions for the data you will have uploaded historically. This feature is offered for content types that are on a per-share basis (ex., EPS).
Alternative places to create a new field
You can also create a field from the field picker in Price Monitor. Type a field name; if it doesn’t exist, the menu will offer you the option to create a new field.
Once created, it is automatically added to the current view on Price Monitor.
Amend a Field (Admins only)
To amend an existing field, press the pencil button in the main Overview page, or press the “Edit Field” button in the Single Field View.
After you have created a field, not everything can be amended. The elements that cannot be changed are greyed out in the Edit field menu.
- the content type can only be changed to other content types of the same nature (Eg: if the field was originally created as a non-periodic number, only non-periodic content types will be available in the Edit field menus). This limitation was introduced to protect the integrity of the data.
- Also, the Excel field code cannot be changed. This is to avoid disrupting models and mapping files created using the Excel field codes.
- Only users defined as Admins have the ability to amend a field.
Delete a field (Admins only)
To delete a field, press the Delete button from the Field Overview page or the “Delete Field” button in Single Field View.
Important note: When deleting a field, every datapoint created for this field will also be permanently deleted.
Note that only users with Admin privilege can delete fields. The buttons to delete fields are not available in the UI for non-Admin (“normal”) users.
Create and Amend Datapoints
Several ways are available to add new datapoints to Sentieo Connect
Add a datapoint from Sentieo Connect Portal
From the Overview page, look for the field you want to create data for and click on it. This will take you to the Single Field View. There, you can find data that has already been created.
To create new datapoints, simply click on “+ Add Datapoint”.
Navigate through your datapoints
In this field view, data is grouped by combinations of [Ticker, Period, and Scenario]. This means all datapoints created by any user, in the user groups you belong to, are grouped in the same stream. Grouping are done in combinations of similar Ticker, Period, and Scenario. For example, If you enter the field “MyRevenue”, all the datapoints created by you and other users in the same user groups for AAPL⇒ for the Period “FY2022″⇒ for the Scenario “Base Case”, are shown to you and grouped together in the same stack.
The main view shows you the most recent datapoint. If you would like to check the datapoint history, click on a value and it will bring up all the datapoints for older observation dates.
Filter and Sort data points
To filter. Click on the funnel icon in the field header to open the filtering menu and filter by a parameter. In the menu, you can here select which values to keep and which to exclude.
To sort. Click anywhere in the header to sort by a parameter. Clicking multiple times rotates between Ascending, Descending, and No Sorting by that parameter.
To multi-sort. Once sorting is active, you can also sort by a second parameter in another column. The table will become sorted by the parameter marked as (1), then as a second level according to the parameter marked (2). You can keep adding as many levels of sorting as you like.
Note. Filtering and sorting only applies to the datapoints on the page being shown on screen. If you uploaded more datapoints than can fit in a single page, these won’t be taken into account.
Add a datapoint from Price Monitor
Any User field displayed on Price Monitor can be edited directly from that section.
Editing a field from Price Monitor effectively creates a new datapoint with the same parameters (ticker, field, period, scenario), for today’s observation date, and with you as the owner.
You can check the result immediately afterwards in the Single Field View of the Sentieo Connect Portal
Upload data in Bulk from Excel
The Excel Uploader is the primary method of uploading data files to Sentieo Connect. The Sentieo Excel Add-In offers a helpful interface that allows you to upload data and review your upload history.
Our support center has instructions to download and install the Add-in here.
Data file format: Should I use Upload Templates or File Mapping?
Sentieo Connect needs to be directed as to the relevant information it should ingest from an uploaded spreadsheet.
For that, you can either upload the file and follow a wizard to identify the relevant datapoints, or add to your workbook a pre-configured template from Sentieo. Each option is better suited to different situations.
- Templates are fast and easy; just link into them the relevant data from your model. It is less cumbersome than the manual mapping process. However, it adds an extra spreadsheet to your workbook, which may be inconvenient or even impossible sometimes (e.g. if you have no control over the source file).
- Manual Mapping does not require you to add a sheet to your workbook. It is mostly useful if you have no control over the source file (eg: it comes from a 3rd-party data provider, or from another software you use). However, you’ll need some training to become familiar with the Table Mapping wizard.
Please follow this link for a step by step walkthrough of the manual mapping process.
All Sentieo Templates are here . We tried to cover multiple common ways of organizing data. Pick the template closer to how your own spreadsheet is organized, so you can link one cell and drag the formula across to help speed up the setup process.
If none of our templates fits your models, please let us know on the support chat. We love the feedback; we want to keep adding templates that work for every use case!
Once you have either added and configured a Template or manually mapped a file, you won’t have to do it again. Subsequent re-uploads of the same file will be automatically detected and ingested.
Upload data in Bulk with FTP
Files sent to Sentieo Connect by SFTP are automatically ingested. As a result, you can easily create fully automated integrations using your data as a source. For example, keep your portfolio synced in Sentieo by asking your portfolio software vendor to send a daily portfolio snapshot to your Sentieo SFTP address.
You can also manually upload files by SFTP. An SFTP client is required; please speak to your IT department. In the SFTP location, simply drag and drop files that carry a template or that have been mapped manually at least once, and it will be automatically ingested.
Where to find your SFTP account credentials?
Look into the Sentieo Connect portal for the “How to upload data” section. You should find the SFTP address as well as your user name and password. If you are not enabled for SFTP access yet, you will not find your credentials here. In that case, please speak to your Customer Success representative and we will enable it for you.
Amend existing datapoints
To amend a datapoint, go to the single field view, find the datapoint you would like to change, press the pencil button, and amend the value.
If you are looking to amend an older datapoint, click first on the datapoint from the single field view, then click on the pencil icon in the pop up showing you historical values.
Delete existing datapoints (Admins only)
Follow the same steps as for amending a datapoint but use the delete button instead.
- To delete the most recent value
- To delete a historical value:
- To delete all the existing datapoints in a field, you need to delete the field itself. Note: all the associated data for you and anyone else in the organization will also be permanently deleted.
Please check the summary of permissions and actions here to familiarize yourself with the exact scope of delete actions in Sentieo Connect Portal.
Create and Manage Scenarios
Scenarios allow you to create multiple hypotheses for the same combination of Ticker, Field, Period, and Date. For example, you could have a “Good”-, “Base”-, and “Bad”-case scenarios.
Sentieo Connect requires at least one Scenario since every datapoint needs to be part of a scenario.
Create a new scenario
In the Sentieo Connect portal, head to the “Scenario Manager” tab and click on “Create Scenario”.
You need to name the scenario, and you can optionally add a description. We recommend writing the description, as it will help you and other team members in your organization use the database more cohesively.
Default scenario (Admins Only)
You can also define what is the “default scenario”. That scenario will be presented by default when creating datapoints or loading them on Screener, Plotter, Price Monitor, or in Excel pulls, if a scenario is not specified.
Make a scenario the default scenario
Move your mouse over a scenario name to reveal the “Make Default” action. Click on it.
Amend or Delete a scenario (Admins only)
You can amend the name and description for an existing scenario, or delete it altogether, using the usual pencil and delete buttons on the left.
Please note that deleting a scenario also deletes every datapoint you and your colleagues have created for that scenario permanently.
Please check the summary of permissions and actions here to familiarize yourself with the exact scope of delete actions in Sentieo Connect Portal.
Manually Mapping a File
Manual Mapping does not require you to add a sheet to your workbook. It is mostly useful if you have no control over the source file (eg: it comes from a 3rd-party data provider, or from another software you use).
Follow the steps below to map the data on a file manually.
Auto-mapping on reuploads
If this is not the first time you are uploading this file and you have already mapped it before, Sentieo Connect will recognize it and offers to process it automatically.
You do not have to remap files unless the relevant data have changed substantially; Sentieo Connect is robust to small alterations such as adding lines and columns, even within the target area.
Step 1. Upload the file.
Start by uploading the file using the Excel plugin or through SFTP.
Sentieo Connect will an invite to start mapping the data if the file does not have an Upload Template sheet and it was never seen before.
Step 2. Provide some additional info about the workbook
- Define a Threshold: When processing the file, you can define an error tolerance to erroneous datapoints. For example, a threshold of 5% means that the upload will be considered successful as long as at least 95 datapoints out of every 100 datapoints uploaded are valid. A valid datapoint is a datapoint for which all the following information is present:
- a ticker,
- a field,
- a period (if the field is periodic),
- an as-of date,
- a scenario,
- an actual datapoint, and
- the datapoint is of the right nature for the selected field (eg: number <> number).
These details can either be directly provided in the table or by using appropriate fallback options (see more about fallbacks below).
- Load An Existing Mapping: Instead of starting the file mapping from scratch, you could base it off a mapping configuration you made previously for another file. You’ll find here all the configurations that have been created by you and your colleagues.
- [Delimiters] (CSV files only): CSV files do not have a standard method of representing the delimitation between cells on the spreadsheet. Some files use commas (,), others use semi-colons (;), or a pipes (|), and so on. Please select which one your file uses.
- [Date Format] (CSV files only): Unlike Excel files, CSV files do not share a standard format for expressing dates. Pick here which one correspond to your files’.
Step 3 – Select the relevant data (1)
In the next step, focus in on the workbook area with the relevant data to be uploaded
- Worksheet: Select the worksheet with the data
- Start Row and Start Column: Indicate the number of the line and column where the data starts
- End Row and Column (both are optional): use only if you want to manually hardcode the end row and/or column of your table.
If you leave those empty, Sentieo Connect automatically re-adapts to the new table size each time the file is re-uploaded. This is useful for time series or if you are gradually adding more lines or columns over time (with more metrics or more periods), for example.
- Indicate if the table has a header line and/or column: header lines and columns will be added to the sides of the preview table and remain visible while you navigate during checking the data.
If the data to upload is on more than one worksheet
In this case, use the top Table pane to add more tables to your mapping and follow the area targetting steps above for each table.
Step 4 – identify the content of lines and columns (2)
By default, every line and column is set to “Data”. Use the header dropdowns to identify what information each line and column contains.
The dropdown offers you all the required defining parameters of a datapoint:
- Field Mnemonic
- As-of Date
If you tag a line with “Ticker”, you are indicating that all cells in that line carry symbols (eg: Sentieo Tickers, Custom Entities or Custom Quotes, or any other identifiers we recognize such as ISIN, CUSIP, BBG ticker, etc..).
If you tag a line or a column with “Field Mnemonic”, you are indicating that all the cells in that line or column carry ticker codes previously created by your organization on Sentieo Connect. These Fields are those that relate to the datapoints in the adjacent lines and columns respectively.
Likewise, If you tag a line or a column with “Period”, you are indicating that all the cells in that line or column carry Periods (eg: FY2021, March-09, etc.) which are related to the adjacent datapoints in that table.
The same applies to Scenarios, As of Dates, and Sources.
Specific field codes
You can also fine all the Custom field codes created in your organization in the dropdown. Use these on a line or column if all the data in said line or column is for a given field, and the name of that field is not explicitly indicated in the header line or column.
Step 5 – Define the fallbacks (3)
Every datapoint needs the following parameters:
- A target Entity
- A Field
- A Period (for periodic fields)
- An Observation Date
- A Value, valid according to the field nature (Eg: number for number)
- A Scenario
- A Source
So for any datapoint in the table does not have all of this information, Sentieo Connect will rely on the fallback values you indicate in this section to fill in the gaps.
In the example used in this walkthrough, only Ticker and As of Date are present in the table, so fallbacks are used for everything else.
Types of fallbacks and available options
For each time of fallback, you can either use a fallback value or instruct Sentieo Connect to fail the datapoint, in one of 3 ways:
- Assume a Ticker: lets you indicate a cell on the worksheet where to find the fallback ticker, or type it manually
- Error: If a datapoint is not clearly met with a ticker based on how the table is organized and mapped, then the datapoint count as an error towards the threshold of acceptance of the overall sheet
- Fail the upload: use this option if you consider that a missing ticker for a datapoint is so crucial that fact alone should fail the overall workbook upload
- Ignore the datapoint: use this option if you consider that a missing ticker for a datapoint is a minor issue so that it does not even count towards the threshold of acceptance of the overall sheet.
- Scenario: The same four options are available for Scenarios: Assume a Scenario, Error, Fail the upload, and Ignore the datapoint.
- Source: The same four options are available for Source: Assume a Scenario, Error, Fail the upload, and Ignore the datapoint.
- Field Code: The same four options are available for Field Codes: Assume a Scenario, Error, Fail the upload, and Ignore the datapoint.
- Observation Date: The same four options are available for the observation Date: Assume a Scenario, Error, Fail the upload, and Ignore the datapoint.
- Watchlist Action: You can optionally upload all the tickers of the table into a watchlist.
- “Replace a watchlist” completely replaces the existing watchlist with this new list of tickers.
- “Update the watchlist” adds to the existing watchlist all the new tickers identified in the table.
The Final Result
This table has a very simple structure and only needed to tag one column (Observation dates), and one line (Tickers) to cover its entirety. However, it does not have all the required parameters, so we had to rely on the fallbacks.
In this case, it is assumed that the scenario for all the uploaded datapoints in this table was “base”, the Source was “LinkedIn”, the Field Code was “UD.Linked_In_Data”, and the watchlist (optional) to update with the ticker list was “LinkedIn Data Coverage List”.
Content type summary
This is a quick summary of all the content types we implemented and what parameters they are set to.
We recommend using pre-built content types are much as possible. Knowing that a field you called “MySuperDuperRevenue” is a “Revenue Estimate” type helps Sentieo know that it can offer you all the transformations and calculations it normally applies to Consensus Estimate history. Another example would be with “MyAwesomeEPS”; as an “EPS Estimates” type, we can automatically apply new stock split adjustments to old data points whenever a new stock split is announced.
In summary, besides helping you create fields quicker, using pre-built content types helps Sentieo deliver you more useful and accurate features.
Field name and Field code character limitations
We sought to minimize limitations around what character or data point length we allow in Sentieo Connect while not compromising on feature and performance. Here is a quick summary of the limitations that were put into place.
Fields in the Create Field Menu
String Datapoint and the Source Label of a Datapoint
Roles and permissions summary
Throughout this walkthrough, we indicated which actions are enabled for Admins only. Here is a quick summary of all-user vs admin rules by module.