INPUT_OBJECT

AccountKPIOrderByInput

Sorting of AccountKPI records. Set exactly one field in each item; list several items to sort by more fields, in order of priority.

link GraphQL Schema definition

  • input AccountKPIOrderByInput {
  • # Unique identifier of entity.
  • id: OrderByEnum
  • # Specifies if the entity is considered deleted.
  • isDeleted: OrderByEnum
  • # Last modification time.
  • modified: OrderByEnum
  • # Creation time.
  • created: OrderByEnum
  • # Account this KPI event relates to. Sorts by fields of the related record, listed
  • # in order of priority.
  • account: [AccountOrderByNestedInput!]
  • # User who triggered the KPI event (e.g. created or archived the account, sent the
  • # first email). Sorts by fields of the related record, listed in order of
  • # priority.
  • client: [ClientOrderByNestedInput!]
  • # Account owner at the time the KPI event occurred. Sorts by fields of the related
  • # record, listed in order of priority.
  • owner: [ClientOrderByNestedInput!]
  • # Sales unit the triggering user belonged to at the time of the event. Sorts by
  • # fields of the related record, listed in order of priority.
  • unit: [SalesUnitOrderByNestedInput!]
  • # Id of the account this KPI event relates to.
  • accountId: OrderByEnum
  • # Id of the user who triggered the event.
  • clientId: OrderByEnum
  • # Id of the account owner at the time of the event.
  • ownerId: OrderByEnum
  • # Id of the sales unit.
  • unitId: OrderByEnum
  • # Revision when entity was lastly changed.
  • revision: OrderByEnum
  • }

link Require by