ProjectFilesByProjectId: Gripp CRM Project Files by Project ID
read only REST
- Catalog:
GrippCrm - Schema:
GrippCrm - Label: Project Files by Project ID
Can only retrieve data.
API Source
- Endpoint:
api3.php
Performance Characteristics
| Characteristic | Value |
|---|---|
| Write rows per minute | 8,930 |
The result can be cached on the client.
Parameters
| Name | Data Type | Required | Default | Documentation |
|---|---|---|---|---|
project. |
`` |
Table Columns
The columns of the table ProjectFilesByProjectId 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 | Marks | Documentation |
|---|---|---|---|---|---|
file_ |
int32 |
File ID | filters on the platform, writable, id |
||
file_ |
varchar2 |
File Search Name | filters on the platform, writable, searchname |
||
parent_ |
int32 |
itgen_gripp_parent_id | filters on the platform, writable, ::ancestor. |
Release Notes
What changed per release in the tables, columns, attributes and capabilities of the driver:
Changes of This Table, 26.0 to 27.0
Table function GrippCrm..ProjectFilesByProjectId is renamed to GrippCrm.GrippCrm.ProjectFilesByProjectId
A statement that names GrippCrm..ProjectFilesByProjectId fails after the upgrade; use GrippCrm.GrippCrm.ProjectFilesByProjectId. The table function has 3 columns. The driver registered its objects without a schema in release 26.0; from 27.0 the schema is GrippCrm.
What to Do
Check statements, views and scripts that use it before the upgrade.
- can break a statement
- importance 5