Please enable JavaScript to view this site.

Made in EU
Freshservice Forums

Freshservice API Data Model

Navigation: Catalog: Freshservice > Schemas > Schema: Freshservice > Tables

StatisticsIncremental: Freshservice Statistics on Incremental Tables

Catalog: Freshservice

Schema: Freshservice

Primary Keys: id

Label: Statistics on Incremental Tables

Documentation:

Tickets.

Can retrieve data and change data using insert, update and delete.

Table Columns

The columns of the table StatisticsIncremental are shown below. Each column has an SQL data type. A new non-null value must be provided for every required column at all times during insert and update.

Name

Data Type

Label

Required

Documentation

action_code

string

 

☐

 

bytes_retrieved

int64

 

☐

 

created_at

datetime

 

☑

 

download_group_name

string

 

☐

 

download_uid

guid

 

☐

 

end_date_utc

datetime

 

☐

 

end_overall_date_last_updated_utc

datetime

 

☐

 

error_message

string

 

☐

 

first_date_last_updated_utc

datetime

 

☐

 

first_ticket_id

int64

 

☐

 

from_cache

boolean

 

☐

 

last_date_last_updated_utc

datetime

 

☐

 

last_ticket_id

int64

 

☐

 

max_date_last_updated_utc

datetime

 

☐

 

max_ticket_id

int64

 

☐

 

min_date_last_updated_utc

datetime

 

☐

 

min_ticket_id

int64

 

☐

 

page_number

int32

 

☐

 

page_registration_date_utc

datetime

 

☐

 

page_rows_added_count

int64

 

☐

 

page_rows_count

int64

 

☐

 

page_rows_overwritten_count

int64

 

☐

 

pages_retrieved

int32

 

☐

 

paging_code

string

 

☐

 

rows_retrieved

int64

 

☐

 

start_date_utc

datetime

 

☐

 

start_overall_date_last_updated_utc

datetime

 

☐

 

success_flag

boolean

 

☐

 

table_name

string

 

☑

 

uid

guid

 

☐

 

updated_since_utc

datetime

 

☐

 

url

string

 

☐

 

 

11-12-2024 09:11 Version 24.0.491-PROD+5130

X

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

  • Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
  • Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
  • Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
  • Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
  • Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
  • Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
  • Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
  • Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.
  
Disclaimer