Intro
The DomoStats Connector allows you to explore how your team is using Domo. Learn about your team’s activities, Projects and Tasks, DataSets, Buzz conversations, and more to find insights and shape your company’s Domo experience. You must have an Admin security role to access the DomoStats Connector or to connect to the DomoStats apps. However, after the DataSets have been created or the app has been deployed, they can be shared with anyone in your organization. You import DomoStats DataSets into the Data Center. This topic discusses the fields and menus that are specific to the DomoStats Connector user interface. General information for adding DataSets, setting update schedules, and editing DataSet information is discussed in Adding a DataSet Using a Data Connector.Prerequisites
To pull in DomoStats DataSets using this Connector, you must have the Admin default security role.Connecting to DomoStats DataSets
This section enumerates the options in the Details pane in the DomoStats Connector page. The components of the other panes in this page, Scheduling and Name & Describe Your DataSet, are universal across most Connector types and are discussed in greater length in Adding a DataSet Using a Data Connector.Details Pane
This pane contains a single Report menu from which to select your desired DomoStats DataSet. See the list of available reports below.| Report Name | Description |
| Accounts | Returns information about the Accounts that are in the instance. |
| Accounts with Permissions | Returns information about the Accounts that are in the instance and what users have access to them. |
| Activity Log | Returns information about team member activities within Domo such as logins, card creation, card viewing, and DataSet creation. When this report is first installed, 30 days’ worth of history is loaded. After this initial run, every time the report runs it will pull in all new records since it last ran, up to 30 days prior. We recommend running this report daily, but it should be run at least once every 30 days. Otherwise, there will be gaps in the data. See reference . |
| AI Chat Sessions | Returns information about AI Chat sessions in your instance. See reference . |
| AI Model Endpoints | Returns information on when the model was used and additional information, including the model tier, source, and status. See reference . |
| AI Models | Returns a list of models and model providers in your instance. See reference . |
| AI Projects | Returns a list of AI projects in your instance. See reference . |
| AI Readiness | Returns information about your data’s AI Readiness. See reference . |
| AI Readiness Details | Returns details about AI Readiness components. See reference . |
| AI Services | Returns a list of AI services and information, including provider and service type. See reference . |
| Alerts | Returns information about Alerts configured in your instance. |
App Studio App Pages | Returns information about app pages inside of App Studio apps in your instance. See reference . |
App Studio Apps | Returns information about App Studio apps in your instance. See reference . |
| AutoML Training Jobs | Included with data science package. |
| Beast Mode Datasource | Returns the Datasource ID linked to each calculated field (Beast Mode) in your instance. A See reference . |
| Beast Modes | Returns information about all Beast Mode calculations in your instance. See Beast Modes DataSet below. |
| Beast Modes used in Beast Modes | Returns information about calculations currently used in other calculations. Learn about nested calculations . |
| Beast Modes used in Cards | Returns information about Beast Modes currently in use in cards. |
| Buzz | Returns information about Buzz usage within Domo such as conversation participants and number of messages posted. |
| Card Datasource | Returns the DataSets that power a card. |
| Card Loads | Returns information about cards and card loads in your Domo environment. See Card Loads DataSet below. |
| Card Pages | Returns the dashboards where at least one card displays. |
| Card Permissions | Returns information about card permissions. |
| Cards | Returns information about all the cards in your Domo environment. |
| Certified Content | Returns information on the certified content. |
| Columns used in Beast Modes | Returns information about which columns are currently in use in a Beast Mode. |
| Connector Failures | — |
| Credit Usage | Returns information on the credit usage. |
| DataFlow Input DataSources | Returns the IDs of inputs to DataFlows. |
| DataFlow Output DataSources | Returns the IDs of outputs from DataFlows. |
| DataFlows | Returns information about DataFlows within your Domo instance, such as DataFlow name, type, status, last updated date, etc. See DataFlows DataSet below. |
| DataFlows History | Returns DataFlow run history information for your Domo instance, such as DataFlow name, run start and end time, whether runs were successful, etc. See DataFlows History DataSet below. Note: This report may have up to a 24-hour window without data. For example, if your report ran at 1 a.m. on 10/10, the report may not pull anything more recent than 1 a.m. on 10/09. |
| DataFlow Tags | — |
| DataSet Access | Returns which users or groups have access to which DataSets and what permission level they have. |
| DataSet Schema | Returns the schema for all DataSets. |
| DataSet Tags | Returns which tags are assigned to which DataSets. |
| DataSets | Returns information about DataSets within your Domo instance, such as DataSet name, owner, connector, last run date, etc. See DataSets DataSet below. |
| DataSets Execution Error | Returns DataSets with errors. |
| DataSets History | Returns DataSet run history information for your Domo instance, such as DataSet name, run start and end time, whether runs were successful, etc. See DataSets History DataSet below. |
| Deleted DataSets | Returns information on the deleted DataSets |
| Grants | Returns information on access that is granted |
| Group Members | Returns one row for each member of each group in Domo. Each row includes the group ID, group name, and member user ID. Only active users and groups appear in this report. System users and system groups are excluded. Groups without members are also excluded. |
| Group Owners | Returns one row for each owner of each group within Domo. Rows list the group ID, owner ID, and owner type (user or group). Only active groups appear in this report. Groups without owners do not appear, including system groups and ad hoc groups. |
| Groups (Beta) | Returns one row for each group in Domo. Each row includes the following:
Only active groups appear in this report. |
| Jupyter Workspaces | Returns information on Jupyter Workspaces. |
| Jupyter Workspace Usage | Returns information on Jupyter Workspaces usage. |
| ML Inference Jobs | Included with data science package. |
| Mobile Activity | Returns a user ID, the user’s mobile device, and their session start date and time. |
| OKR Key Results (included with Domo Goals) | Returns information about the key results/metrics that have been created in Domo Goals. See OKR Key Results DataSet below. |
| OKR Objectives (included with Domo Goals) | Returns information about the objectives/goals that have been created in Domo Goals. |
| Pages with Multiple Owners | Returns information of each owner of a Page broken out per row. |
| People | Returns information about users in your Domo instance, such as user name, security role, contact information, and most recent login date. See People DataSet below. |
| Project Stages | Returns information about project stages in your Domo instance. See Project Stages DataSet below. |
| Projects | Returns information about projects in your Domo instance, such as project name, owner, associated tasks, etc. See Projects DataSet below. |
| Publish | Included with Domo Everywhere. |
| Publish Event Logs | Included with Domo Everywhere. |
| Role Grants | Returns grants assigned to each role in the instance. |
| Roles | Returns information about roles. |
| Sandbox Commits | Returns information about Sandbox commits. |
| Sandbox Content Mappings | Returns information about Sandbox content mappings for promotions. |
| Sandbox Promotions | Returns information about Sandbox promotions. |
| Sandbox Repository Access | Returns which Domo domains have been granted access to a repository. |
| Sandbox Repository Permissions | Returns the permission level for all Sandbox repositories. |
| Scheduled Report Recipients | Returns information about recipients for scheduled reports. |
| Scheduled Reports | Returns information about scheduled reports. |
| Task Center | Returns information about task usage in your instance. Each row in the DataSet represents a specific task. See Task Center DataSet below for the full schema. |
| Task Owners | Returns information about task owners in your Domo instance. See Task Owners DataSet below. |
| Tasks | Returns information about tasks in your Domo instance, such as task name, parent project, assignees, etc. See Tasks DataSet below. |
| Usage Metrics | Returns information about the usage of Domo, including rows under management, connector executions, Jupyter usage, and so on. |
| User Activity — AI Services Billing | Returns User Activity in relation to AI Services Billing info. |
| User Activity | Returns User Activity, similar to the Activity Log in the Admin section. |
| User Landing Resource |
|
| Variables | Returns information about existing Variables in your instance. |
| Variables used in Beast Modes | Returns information about which Variables are currently in use in a Beast Mode. |
| View Inputs | Returns the ids for inputs to views. |
| Workbench | Returns information about Workbench job statuses, last run times, which machines are running the jobs, what DataSets are powered by the jobs, and schedule type. See Workbench DataSet below. |
| Workflows | Returns information about Workflows usage in your instance. Note: A DataSet for the Workflows DomoStats report can only be created once per instance. See Workflows DataSet below for schema details. |
Other Panes
For information about the remaining sections of the connector interface, including how to configure scheduling, retry, and update options, see Adding a DataSet Using a Data Connector.Locating DomoStats DataSets
After a DataSet is created, you can locate the DataSet through filters and tagging. This helps keep DataSets organized and accessible.- In the navigation header, select Data.
-
Select
DataSets from the
navigation rail.
- In the Search bar, type the name of your DataSet. You can also locate DataSets using filters.
- In the Search bar, select Add Filter.
- Choose Type and enter DomoStats.
Tagging a DomoStats DataSet
Locating and organizing your DataSets is made possible by tagging. Tagging groups the DataSets in collections that can be found using the Tag filter.- Locate the DataSet in Domo. (See the previous section, Locating DomoStats DataSets, for a step-by-step guide.)
- Select + Add Tag under the DataSet’s name.
- Choose from the list of available tags, or create a new tag using the search feature.
- Select + next to Create new tag.
- Select Save.
DataSet Fields
This section gives field-by-field descriptions for certain DomoStats reports DataSets.Activity Log DataSet
| Field | Description | ||||||||||
| Object_Name | The name of the object that received an action. | ||||||||||
| User_ID | The ID of the person or thing that performed an action. | ||||||||||
| Source_ID | The ID of the type. For a simplified example, let’s say a user added a card to a page. You would get these two actions on an event, and both would be returned on the DataSet.
| ||||||||||
| Name | The name of the object that performed an action. | ||||||||||
| Action | The event that took place. The following actions may be logged here:
| ||||||||||
| Object_Type | Clarifies what the object is. | ||||||||||
| Object_ID | The ID of the object. | ||||||||||
| Type | The type of person or thing that performed an action. | ||||||||||
| Event_Time | The time at which the event occurred. The audit endpoint records/returns it in UTC, but the connector converts it to the user’s time zone. | ||||||||||
| Authentication_Method | This column may contain data for historical records but is NULL for newly logged activities. | ||||||||||
| IP_Address | — | ||||||||||
| Device | — | ||||||||||
| Browser_Details | — | ||||||||||
| _BATCH_ID_ | |||||||||||
| _BATCH_LAST_RUN_ | — |
AI Chat Sessions DataSet
Field | Description |
|---|---|
Session Id | The unique identifier for the chat session. |
Request Id | The unique identifier for the specific user request. |
User Id | The unique identifier for the user initiating the request. |
DataSource Ids | The identifiers for data sources involved in the request (if any). |
Ignorable DataSource Ids | The identifiers for data sources found in |
Card Ids | The identifiers for UI components used to help formulate the response. |
Page Ids | The page identifiers related to the request. |
Filters | Any filters applied during the session. |
TOE | The identifier of the execution, used by Domo for troubleshooting. |
Request | The text of the user’s query. |
Request Timestamp | The timestamp for when the request was made. |
Response | The chat’s response to the user request. |
Response Timestamp | The timestamp for when the response was generated. |
Duration | The time taken to generate the response in milliseconds. |
Error Message | The description of the error. |
Error Code | The error classification. |
Response Status | The numeric code representing the outcome. Example: |
Models | The model(s) used to generate the response. |
BATCH_ID | |
BATCH_LAST_RUN | Timestamp of the last batch process run. |
AI Model Endpoints DataSet
AI Models DataSet
Field | Description |
|---|---|
| Model Name | The model name. |
Description | The model’s description. |
Projects | The number of projects the model has been added to. |
Created | The date the model was created. |
Owner | The user ID of the model owner. |
Model ID | The numeric identifier for the model. |
Provider | The model provider.
|
Project IDs | The IDs for the projects the model has been added to. |
AI Projects DataSet
Field | Description |
|---|---|
Project Id | The numeric identifier for the project. |
Project Name | The name of the project. |
Description | The project’s description. |
Created | The date the project was created. |
Updated | The last date the project was updated. |
Owner | |
Number of Models | The number of models the project has been added to. |
AI Readiness
AI Readiness Details
AI Services DataSet
Field | Description |
|---|---|
Provider | The model service provider. Example values:
|
Service | The AI service used in the model. Examples values:
|
Model Name | The model’s name. |
Model Id | The date the model was created. |
Description | |
Default | This field displays if the model is used by default in the associated service. |
Domo Provided | This field displays if Domo has provided the model or if it is an externally provided model. |
App Studio App Pages DataSet
Field | Description |
|---|---|
App ID | The numeric identifier for the app. |
App Page ID | Identifier for the page in the App Studio app. |
App Page Title | |
Number of views | The number of views of the page in the App Studio app. |
App Studio Apps DataSet
Field | Description |
|---|---|
App ID | The numeric identifier for the app. |
App Title | The title/name of the app in your instance. |
Owner ID | The numeric identifier for the app owner. |
Owner Type | The type of app owner. |
Created | The date and time when the app was created. |
Locked | Indicates whether the app is locked. |
The identifier for the batch. | |
_BATCH_LAST_RUN_ | The date and time when the batch was last run. |
Beast Mode Datasource
Beast Modes DataSet
Field | Description |
|---|---|
ID | The numeric identifier of the calculation. |
Name | The name of the calculation. |
LinkedID | The identifier of the card or DataSet to which the calculation is saved. |
LinkedType | The type of location type where the calculation is saved.
|
The name of the card or DataSet to which the calculation is saved. | |
ArchivedStatus | The status of the calculation.
|
Validity | The validity status of the calculation.
|
Card Loads DataSet
Field | Description |
|---|---|
| cardId | The numeric identifier of the card. |
context | The location where the card is being loaded. Example: |
date | The date when the card was loaded. Example: |
errorCode | The status message for the card load. Options include: |
platform | The platform where the card is being loaded. Options include: |
totalCount | Count of card loads with these same details on this date. |
totalDuration | The total duration of all combined card loads on this date. |
_BATCH_ID_ | The numeric identifier for the batch as a floating decimal. |
_BATCH_LAST_RUN_ | The date and time when the batch was last run. |
Card Permissions DataSet
| Field | Description |
| cardId | The ID of the card to check permissions for. |
| entity type | The entity (user or group) for whom permissions exist. |
| entityId | The user or group ID of the entity for whom permissions exist. |
| permission mask | A numerical representation of the set of permissions granted to a user or group. |
| Permission | A permission mask followed by a visual breakdown of the permissions granted to a user or group. D = Delete A = Admin |
Certified Content Known Limitation
There is a limitation if you attempt to combine a Certified Content DomoStats DataSet with an Activity Log DomoStats DataSet.DataFlows DataSet
DataFlows History DataSet
| Field | Description |
| ID | An ID for a specific run of the DataFlow. |
| DataFlow ID | The ID number for the DataFlow. |
| Display Name | The name of the DataFlow. |
| Type | Returns the DataFlow type, either ETL, MYSQL, or REDSHIFT. |
| Status | Returns the status for the DataFlow run, either CANCELLED, FAILED, REJECTED, or SUCCESS. |
| Execution Type | Returns the type of execution, either DATA_UPDATE, MANUAL, RETRY, or SCHEDULED. |
| Start Time | A timestamp for the time the DataFlow started executing. |
| End Time | A timestamp for the time the DataFlow stopped executing. |
DataSets DataSet
| Field | Description | ||||||||||
| Status | The status for the DataSet. The following statuses may appear here:
| ||||||||||
| ID | The unique identifying value for the DataSet. | ||||||||||
| Owner_User_ID | The unique identifying value for the person who owns the DataSet. A DataSet owner is either the person who created the DataSet or the person whom ownership was assigned to. | ||||||||||
| Created_Date | The date on which the DataSet was run for the first time. | ||||||||||
| Last_Run_Date | The date on which the DataSet last successfully completed a run. | ||||||||||
| Name | The current name given to the DataSet. | ||||||||||
| Schedule | The schedule option that has been configured for this DataSet. The following options may appear here:
| ||||||||||
| Import_Type | The source for the DataSet. Could be a Connector, DataFlow, API, etc. | ||||||||||
| Source_Type | UNDER CONSTRUCTION |
DataSets History DataSet
| Field | Description | ||||||||||||
| Stream ID | A Domo-specific ID to map to the stream. | ||||||||||||
| Execution ID | The ID for a specific run of the DataSet. | ||||||||||||
| Datasource ID | A Domo-specific datasource ID | ||||||||||||
| Status | The status for the DataSet history item. The following statuses may appear here:
| ||||||||||||
| Execution Type | The type of execution. The following execution types may appear here:
| ||||||||||||
| Start Time | The time the DataSet started running. | ||||||||||||
| End Time | The time the DataSet finished running, went into an error state, or became invalid. |
OKR Objectives DataSet
The fields in this section use “Objectives” and “Key Results”. Your organization may refer to them as goals, metrics, or something else depending on your Goals Admin Settings. For more information about using the DomoStats Connector with Goals, see Accessing Goals Data.| Field | Description |
| ID | The unique identifier of the objective. |
| Name | The name of the objective. |
| Description | The description of the objective. |
| State | The current state of the objective. Possible states are listed below: OPEN: The objective’s expiration date has not elapsed and the objective has not been marked complete. EXPIRED: The objective’s expiration date has elapsed. CLOSED: The objective has been marked complete. |
| Owner ID | The ID of the individual user or group that owns the objective. When multiple individuals or groups own an objective, the ID of the first owner is populated in this field. |
| Owner Type | Indicates whether or not the objective owner is an individual user or group. Possible types are listed below: USER: A Domo user GROUP: A Domo group |
| Type | The type of objective. Possible values are: PERSONAL TEAM COMPANY |
| Team ID | The ID of the Domo group that is assigned to the objective. (For Team-type objectives) |
| Parent ID | The ID of the parent objective, if applicable. |
Parent IDs | The IDs of the parent objectives if the objective has multiple parents, if applicable. |
Multiple Parents | Indicates whether or not the objective has multiple parents. |
Period ID | The ID of the period that the objective is active (based on Start and expiration date). |
Period IDs | The IDs of periods if an objective is active for multiple periods. |
Company ID | The ID of the organization that is assigned to the objective. (For Company-Type objectives) |
Company IDs | The ID of each Company-type objective if linked to multiple Company-type objectives. |
Self Assessment | The optional self assessment submitted when marking an objective complete. |
Confidence | A numerical value based on the objective status. Values with their associated status are listed below: 1: ON TRACK 0.5: NEEDS ATTENTION 0: AT RISK |
Likes | The number of likes the objective has received. |
Dislikes | The number of dislikes the objective has received. |
Subscriptions | The number of users who have subscribed to the objective. |
Company Objective | Indicates if the objective is a Company-type objective. |
Start Date | The start date of the objective. |
Expire Date | The end date of the objective. |
Impact Start Date | (DEPRECATED) The date when the impact of the achieved objective is expected to begin. |
Impact End Date | (DEPRECATED) The date when the impact of the achieved objective is expected to end |
Tags | A list of tags associated with the objective. This list is separated by commas. |
Tag Categories | A list of tag categories associated with items in the Tags field. This list is separated by commas. |
Created Date | The date the objective was created. |
Creator ID | The ID of the user who created the objective. |
Modified Date | The date/time the objective was last modified. If the objective has not been modified, this will be the date and time the objective was originally created. |
Modifier ID | The ID of the user who modified the objective. If the objective has not been modified, this will be the ID of the user who created the objective. |
Owners | A comma-separated list of the ID and Type of the user or group that owns the objective. For example, if user ID 12345678 owns the objective, the field will contain the value 12345678:USER. If group 54231564 owns the objective then the field will contain the value 54231564:GROUP. |
Assigned Team IDs | A comma-separated list of the Domo group IDs that the objective has been assigned to. |
_BATCH_ID_ | An incremental batch number representing each DataSet update. |
_BATCH_LAST_RUN_ | The date and time that the DataSet was last run. |
OKR Key Results DataSet
The fields in this section use “Objectives” and “Key Results”. Your organization may refer to them as goals, metrics, or something else depending on your Goals Admin Settings. For more information about using the DomoStats Connector with Goals, see Accessing Goals Data.| Field | Description |
| ID | The unique identifier of the key result. |
| Name | The name of the key result. |
| Description | The description of the key result. |
| State | The current state of the key result. Possible states are listed below: OPEN: The key result’s expiration date has not elapsed and the key result has not been marked complete. EXPIRED: The key result’s expiration date has elapsed. CLOSED: The objective that the key result belongs to has been marked complete. |
| Owner ID | The ID of the individual user or group that owns the key result. When multiple individuals or groups own a key result, the ID of the first owner is populated in this field. |
| Owner Type | Indicates whether or not the key result owner is an individual user or group. Possible types are listed below: USER: A Domo user GROUP: A Domo group |
| Objective ID | The ID of the objective that the key result belongs to. |
| Card ID | The ID of the card that the key result is linked to (for automatic/card-based key results). |
| Alert ID | A unique ID generated for each key result that is linked to a card. |
| Completion | A percentage representing the progress of the key result as measured by the relationship of the actual value to the target value. The completion is calculated in the following ways: Automatic, card-based key results: Progress is driven based on values in the card relative to a target. Manual/percent completion-based key results: Value is determined based on the percent completion specified in the key result slider bar. Manual/choose your own value key results: Progress is determined based on the actual value of the key result divided by the target of the key result. Projects and Tasks-based key results: Progress is determined by how many projects/tasks have been completed completed in the Projects and Tasks feature. |
| Pacing | When enabled, this field shows the completion of the key result as a percentage compared to the percentage of time that the key result has been open (time between start and end date). |
| Start Value | The initial value of the key result. |
| Current Value | The current value of the key result. |
| Target Value | The target value of the key result |
| Weight | (NOT USED) |
| Fixed Weight | (NOT USED) |
| Manual Type | For manually-managed key results, this field indicates the type of the key result. Possible values are listed below: VALUE: Key result measured with a single value. SCALE: Key result measured using a percent completion scale. PROJECT_AND_TASK: Key result associated to a Domo project. |
| Unit Type | The data type of the key result’s value and target. Possible values include: NUMERICAL PERCENT |
| Project ID | The ID of the project that is linked to the key result (only applicable to Projects and Tasks-based key results). |
| Likes | The number of likes the key result has received. |
| Dislikes | The number of dislikes the key result has received. |
| Start Date | The start date of the key result. |
| Expire Date | The end date of the key result. |
| Cure Period | Indicates when changes to the key result will no longer be tracked. |
| Tags | A comma-separated list of tags associated with objective. |
| Tag Categories | A comma-separated list of tags associated with objective. |
| Created Date | The date the objective was created. |
| Creator ID | The ID of the user who created the objective. |
| Modified Date | The date/time the objective was last modified. If the objective has not been modified, this will be the date and time the objective was originally created. |
| Modifier ID | The ID of the user who modified the key result. If the objective has not been modified, this will be the ID of the user who created the it. |
| Owners | A comma-separated list of the ID and Type of the user or group that owns the key result. For example, if user ID 12345678 owns the objective, the field will contain the value 12345678:USER. If group 54231564 owns the key result, the field will contain the value 54231564:GROUP. |
| _BATCH_ID_ | An incremental batch number representing each DataSet update. |
_BATCH_LAST_RUN_ | The date and time that the DataSet was last run. |
People DataSet
If any of the “personal information” fields (name, email, location, etc.) return blank in this DataSet, you can fill in the missing information in the user’s Profile page or their page in Admin Settings > People. For more information, see Specifying Your Personal Profile Information.| Field | Description |
| Department | The user’s department within your organization. |
| Display Name | The name used to represent the user within Domo. |
| Role | The user’s role within your organization. |
| Title | The user’s title within your organization. |
| The user’s email address. | |
| Alternate Email | The user’s alternate email address. |
| Phone Number | The user’s personal phone number. |
| Desk Phone Number | The user’s desk phone number. |
| Employee Number | The user’s employee number within your organization. |
| Location | The company location the user has been assigned to. |
| Locale | UNDER CONSTRUCTION |
| Timezone | The user’s time zone. |
| Role ID | A Domo-generated ID for a specific role. |
| User ID | A Domo-generated user ID for each person. |
| Last Login | A timestamp for the last time this user logged in. Login is measured by any regular, SSO, or mobile login. To count as a login for mobile, a person must actually log out of the instance and log back in. Opening and closing the app does not count as a login. |
| Password Created | A timestamp for when a user’s password was created. This gets updated when the password is updated. |
| Account Locked | Returns a “True” value if the account is locked. |
| Profile Picture | Returns a “True” value if a profile picture has been added in the user’s Profile page or on his/her page in Admin Settings > Governance > People . |
| Org Chart | Returns a “True” value if the user has been added as a report on their company org chart in the Profile page. |
| Two Factor Enabled | Returns a “True” value if the company has enabled two-factor authentication as an option in Admin Settings > Authentication > Authentication and the user has chosen to have two-factor enabled in their Settings menu (available via clicking the Gear menu under their profile picture). |
| Created Date | A timestamp for the date the user was added to the system. |
| Last Updated Date | A timestamp for the date the user’s information was last updated. |
Project Stages DataSet
| Field | Description |
| Priority | Defines the order in which the lists or stages are shown. Smaller numbers are on the left. |
| Project_id | ID number for the project. |
| Project_name | Name of the project. |
| List_name | Name of the list. |
| List_type | Type of the list. |
| Project_list_id | ID number of the list. |
| Created | Person who created the project. |
| Updated | The time when the list was last edited (e.g. moved, renamed, etc.). |
| Active | Returns “True” if the list or stage hasn’t been archived. |
Projects DataSet
| Field | Description |
| Created_by_user | The person who created the project. |
| Project_id | The ID number for the project. |
| Created | Project creation date and time. |
| DueDate | Due date for the project. |
| Created_by | User ID of the person who created the project. |
| Project_name | Name of the project. |
| Description | Description for the project, if one has been specified. |
| Active | Returns “True” if the project is currently viewable. |
| Deleted | Returns “True” if the project has been deleted. |
Task Center DataSet
| Field | Description |
| Task ID | The unique numeric identifier for the task. |
| Task identifier | The field value(s) configured as task identifier(s). Learn about task identifiers . |
| Form Name | The name of the form being used in the task. |
| Form ID | The unique identifier for the form. |
| Task status | The current status of the task. |
| Queue | The name of the queue where the task is located. |
| Queue ID | The unique identifier for the queue. |
| Created On | The date the task was created. |
| Completed On | The date the task was completed. |
| Completed By | The unique identifier for the person who completed the task. |
| Assignee | The unique identifier for the person or group assigned to the task. |
| Assignee Type | The type of assignee assigned to the task. Options include: |
| Source ID | The unique identifier for the source that generated the task. |
| Source Entity | The entity type of the source that generated the task. |
| Updated On | The date of the most recent update to the task. |
Task Owners DataSet
| Field | Description |
| ProjectTaskName | Name of the task. |
| ProjectName | Name of the parent project for the task. |
| ProjectListId | ID number of the list in which the task is found. |
| ProjectListName | Name of the list in which the task is found. |
| ProjectListType | Type of list in which the task is found. |
| ProjectTaskID | ID number for the task. |
| ProjectID | ID number for the parent project of the task. |
| Created | Date and time the task was created. |
| AssignedBy | ID number of the person who assigned the task. |
| AssignedByName | Name of the person who assigned the task. |
| AssignedTo | ID number of the person the task has been assigned to. |
| AssignedToName | Name of the person the task has been assigned to. |
Tasks DataSet
| Field | Description |
| DueDate | Due date for the task. |
| Project_id | ID number for the parent project for the task. |
| ProjectListId | ID number of the list the task is found in. |
| ProjectListName | Name of the list the task is found in. |
| ProjectListType | Type of the list the task is found in. |
| ProjectTaskId | ID number for the task. |
| ProjectTaskName | Name of the task. |
| Created | Date and time the task was created. |
| Updated | Date and time the task was last updated. |
| ProjectName | Name of the parent project for the task. |
| CreatedBy | User ID of the person who created the task. |
| CreatedByName | Name of the person who created the task. |
| Owner | The ID number for the task owner. The task owner is the creator by default, but can be changed to anyone in the instance. |
| OwnerName | The name of the person who created the task. In the case that the original owner reassigned ownership, then it is the name of the new owner. |
| Priority | The order in which the task shows up on the task board. Lower priority numbers are above higher priority numbers. |
| Active | Returns “True” if the task hasn’t been archived. |
| Description | The description of the task, if one has been specified. |
| Contributors | Individuals assigned to work on the task. |
User Activity — AI Services Billing
| Field | Description |
| Date | The date of the AI Service event. |
| SKU | The Domo Consumption SKU for the AI Service. |
| Entity Type | The action taken in Domo. |
| Entity ID | The unique ID of the action. |
| Usage Unit | The unit of measure for the action. |
| Usage Quantity | The number of actions recorded. |
Workbench DataSet
| Field | Description |
| Workbench Agent | The name of the machine running the Workbench job. |
| Owner ID | The ID number of the owner of the job. |
| DataSet ID | The value that is the identifier for the DataSet. |
| DataSet Name | The name of the DataSet. |
| Job Name | The name of the job. |
| Job Status | The status of the job (Ex. success, fail) |
| Created Date | The date the job was created. |
| Last Run | The date when the job last ran. |
| Next Run | The date when the job will run next. |
| Last Successful Run | When the job ran last successfully. |
| Update Method | The update method used for the DataSet. (Ex. Append, Replace) |
| Rows Updated | The number of rows that were updated. |
| Schedule Type | Shows the schedule type (Ex. manual, custom) |
Workflows DataSet
Field | Description |
|---|---|
Workflow_Name | The name of the workflow. |
Workflow_Version | The workflow version number. |
Execution_ID | The identifier for a specific execution. |
Model_ID | The identifier for the workflow model. |
Trigger_Type | The type of trigger that started the workflow execution. |
Trigger_ID | The identifier of the trigger that started the workflow execution. |
Created_By | The name of the person who created the workflow. |
Started_By | The name of the person who started the workflow execution. |
Deployed_By | The name of the person who deployed the workflow version. |
Workflow_Status | The status of the workflow execution. |
Start_Time | The time the workflow execution was started. |
End_Time | The time the workflow execution ended. |
Cycle_Time | The duration of the workflow execution from start time to current state. |
Qualifying_Tasks | The number of partial credits the workflow has accumulated during its execution. (These are for any executed start shape, automated function, or User Task.) |