Ordering
Ordering enables a user to specify how the query response should be arranged.
By default, Oracle Textura Payment Management arranges query response containing various objects in descending order based on their ID field values with the following graph exceptions:
- Organization: Orders by "texturaCustomerNumber"
- InvoiceApproval: Orders by "dateModified"
- ProjectUserRoles: Orders by "userid"
Graph | OrderBy | Asc/Desc |
|---|---|---|
Payment | id | DESC |
Invoice | id | DESC |
Disbursable | id | DESC |
Contract | id | DESC |
User | id | ASC |
Project | id | DESC |
Draw | id | DESC |
PaymentHold | id | DESC |
TpaProgram | id | DESC |
ChangeOrder | id | DESC |
LienWaiver | id | DESC |
Organization | texturaCustomerNumber | DESC |
InvoiceApproval | dateModified | DESC |
SupplierTrackingProgram | id | DESC |
SupplierTrackingProgramValue | id | DESC |
SupplierTrackingContractorValue | id | DESC |
SupplierTrackingSelectedValue | id | DESC |
BudgetLines | id | DESC |
ManualContract | id | DESC |
OrganizationLevelHold | id | DESC |
ProjectUserRole | userid | DESC |
Last Published Friday, September 5, 2025