> ## Documentation Index > Fetch the complete documentation index at: https://developers.cmicglobal.com/llms.txt > Use this file to discover all available pages before exploring further. # getUdfData > # GET /jersey/v1/user-defined-fields — Get UDF Field Values ## Overview This endpoint returns all user-defined field (UDF) labels, their physical column names, and the current stored values for a specific record. You identify the record by passing the table name and its business keys. The endpoint works for any UDF-enabled table in CMiC — Projects, Jobs, Vendors, Cost Items, and so on — without any object-specific code. | Property | Value | | --- | --- | | URL | `{base_url}/sys-rest-api/jersey/v1/user-defined-fields` | | Method | `GET` | | Produces | `application/json` | | Success Status | `200 OK` | | Auth | Basic (`Authorization: Basic {credentials}`) | --- ## Notes Authentication and authorization are required for all calls. `schemaName` defaults to `DA` if not supplied. You only need to pass it if you are working in a different schema. `objectKey1` is always required. Additional keys (`objectKey2` through `objectKey10`) are only needed when the table uses a composite key — for example, a Cost Item needs both Company Code and Item Code. If the parent record does not exist in the database, the endpoint returns a 400 error. If no UDF definition exists for the table, it also returns a 400. The response will include an error code and a human-readable message in both cases. Audit columns (`createDate`, `createUser`, `updateDate`, `updateUser`) are populated from the UDF value row itself, not from the parent table. --- ## UI Navigation User-defined fields are custom fields that are attached directly to the object they belong to. They appear on the object's own screen — there is no separate standalone navigation path for them. For example, UDFs for a Project appear on the Project record itself, and UDFs for a Job appear on the Job record. --- ## Finders The following finders are available to identify and retrieve a specific record. This endpoint always returns a single record. There is no list mode — you must supply enough key information to identify exactly one parent record. The combination of `tableName` and the business keys is what acts as the finder. | Finder Parameter | Required | How It Narrows the Result | | --- | --- | --- | | `tableName` | Yes | Tells the endpoint which UDF-enabled table to look in (e.g. `PROJ`, `JCJOB`, `CIITEM`, `JCCOST`). Every call must include this. | | `objectKey1` | Yes | The first (and often only) business key of the parent record. For a Project this would be the Company Code. For a single-key table this alone identifies the record. | | `objectKey2` | Depends | Required when the table uses a composite key. For a Project, this would be the Project Number. For a Cost Item, the Item Code. | | `objectKey3` through `objectKey10` | Depends | Only needed for objects with three or more key parts. Most objects use one or two keys. Pass `null` or omit any slot you do not need. | | `schemaName` | No | Defaults to `DA`. Only supply this if your data lives in a different schema. | **Single-key example** — retrieve UDFs for Job `JOB-001` in company `01`: ``` GET .../v1/user-defined-fields?tableName=JCJOB&objectKey1=01&objectKey2=JOB-001 ``` **Composite-key example** — retrieve UDFs for Cost Item `BOLT-123` in company `01`: ``` GET .../v1/user-defined-fields?tableName=CIITEM&objectKey1=01&objectKey2=BOLT-123 ``` If you are unsure what `objectKey1` and `objectKey2` mean for a given table, call the definition endpoint first: ``` GET .../v1/user-defined-fields/definition?tableCode=CIITEM_K ``` That tells you the label for each key slot before you make the data call. --- ## Query Standards | Key | Description | | --- | --- | | `tableName` | Required. Identifies which UDF-enabled table to query. | | `objectKey1` | Required. First part of the business key that uniquely identifies the parent record. | | `objectKey2` through `objectKey10` | Optional. Additional key parts for composite-key tables. Unused slots can be omitted. | | `schemaName` | Optional. Database schema. Defaults to `DA`. | --- ## Attributes ### Response — Top Level | Field | Type | Description | Example | | --- | --- | --- | --- | | `schemaName` | String | Schema that owns the table | `DA` | | `tableName` | String | Table the UDFs belong to | `PROJ` | | `objectKey1` | String | First business key value | `MAIN` | | `objectKey2` through `objectKey10` | String | Remaining key values (null if unused) | `P001` | | `objectKeyName1` | String | Column name behind objectKey1 | `PROJ_COMP_CODE` | | `objectKeyName2` through `objectKeyName10` | String | Column names behind remaining keys (null if unused) | `PROJ_NUM` | | `fieldCount` | Integer | Number of UDF fields returned | `5` | | `createDate` | String (ISO 8601) | Date the UDF value row was first created | `2025-03-10T09:00:00-04:00` | | `createUser` | String | User who created the UDF value row | `JSMITH` | | `updateDate` | String (ISO 8601) | Date the UDF value row was last updated | `2026-06-01T14:22:00-04:00` | | `updateUser` | String | User who last updated the UDF value row | `BWILSON` | | `fields` | Array | List of UDF field entries — see below | | ### Response — fields\[\] Array | Field | Type | Description | Example | | --- | --- | --- | --- | | `fieldName` | String | Human-readable label configured for this UDF slot | `Project Category` | | `columnName` | String | Physical column name in the UDF value table | `UEV_CODE1` | | `value` | String | Current stored value. `null` if nothing has been saved yet | `COMMERCIAL` | --- ## Example ### Request ``` GET {base_url}/sys-rest-api/jersey/v1/user-defined-fields ?tableName=PROJ&objectKey1=MAIN&objectKey2=P001 Authorization: Basic {credentials} ``` ### Response — 200 OK ``` { "schemaName": "DA", "tableName": "PROJ", "objectKey1": "MAIN", "objectKey2": "P001", "objectKey3": null, "objectKey4": null, "objectKey5": null, "objectKey6": null, "objectKey7": null, "objectKey8": null, "objectKey9": null, "objectKey10": null, "objectKeyName1": "PROJ_COMP_CODE", "objectKeyName2": "PROJ_NUM", "objectKeyName3": null, "createDate": "2025-03-10T09:00:00-04:00", "createUser": "JSMITH", "updateDate": "2026-06-01T14:22:00-04:00", "updateUser": "BWILSON", "fieldCount": 3, "fields": [ { "fieldName": "Project Category", "columnName": "UEV_CODE1", "value": "COMMERCIAL" }, { "fieldName": "Budget Flag", "columnName": "UEV_CODE2", "value": "Y" }, { "fieldName": "Review Date", "columnName": "UEV_DATE1", "value": null } ] } ``` --- ## Error Codes | HTTP | Error Code | Reason | | --- | --- | --- | | 400 | `SD-000375-ERR` | `tableName` or `objectKey1` was not provided | | 400 | `SD-000376-ERR` | Parent record not found for the supplied keys | | 400 | `SD-000377-ERR` | No UDF definition exists for this table | | 500 | — | Unhandled database or server error | ## OpenAPI ````json GET /sys-rest-api/jersey/v1/user-defined-fields { "openapi": "3.0.0", "info": { "title": "API Catalog", "description": "", "version": "1.0.0" }, "servers": [ { "url": "https://mobtest.cmiccloudr12.com/cmictestrti", "description": "CMIC API Server" } ], "security": [ { "cmicBasicAuth": [] } ], "tags": [ { "name": "Highlights" }, { "name": "Asset Management | Equipment" }, { "name": "Asset Management | Fixed Assets" }, { "name": "Asset Management | Purchase Order" }, { "name": "Asset Management | Inventory" }, { "name": "Asset Management | Requisition" }, { "name": "Asset Management | Purchase Change Order" }, { "name": "Bim Model" }, { "name": "Bim Model Revision" }, { "name": "Bim Tag Model" }, { "name": "Bim Tags" }, { "name": "Bim FileUpload Jersey" }, { "name": "Core System | Business Partners" }, { "name": "Core System | Business Partner Addresses" }, { "name": "Core System | Bank" }, { "name": "Core System | Currency" }, { "name": "Core System | Exchange Rates" }, { "name": "Core System | Global Table Text Codes" }, { "name": "Core System | Global Table Regions" }, { "name": "Core System | Terms" }, { "name": "Core System | System Contact" }, { "name": "Core System | Weight Measures" }, { "name": "Core System | Field User Defined Classifiers" }, { "name": "Core System | User Defined Classifiers by Object" }, { "name": "Core System | User Extension Definitions by Object" }, { "name": "Core System | User Extention Field Data Value" }, { "name": "Core System | User Extension Values by Object" }, { "name": "Core System | User System Role" }, { "name": "Core System | User Project Role" }, { "name": "Core System | Documents by Object" }, { "name": "Core System | Audit Status Log by Object" }, { "name": "Core System | Licensed Users" }, { "name": "Core System | Company Access" }, { "name": "Core System | Copy User Settings" }, { "name": "Core System | User Maintenance" }, { "name": "Core System | User Roles" }, { "name": "Core System | Security Groups" }, { "name": "Core System | Job/Project Security" }, { "name": "Core System | Weight Measure with Conversions Code" }, { "name": "Core System | Weight Measure Conversions Code" }, { "name": "Core System | User-defined-fields" }, { "name": "Core System | User-extension" }, { "name": "ECM and Workflow | Image Manager" }, { "name": "Financials | General Ledger" }, { "name": "Financials | Accounts Payable" }, { "name": "Financials | Accounts Receivable" }, { "name": "Preventative Maintenance | Issue Work Orders" }, { "name": "Preventative Maintenance | Issue Work Items" }, { "name": "Preventative Maintenance | Issue Work Budgets" }, { "name": "Preventative Maintenance | Issue Priorities" }, { "name": "Preventative Maintenance | Issue Status" }, { "name": "Preventative Maintenance | Issue Types" }, { "name": "Preventative Maintenance | Accumulative Equipment" }, { "name": "Preventative Maintenance | Work Orders" }, { "name": "Preventative Maintenance | Work Items" }, { "name": "Preventative Maintenance | Work Budgets" }, { "name": "Preventative Maintenance | Priorities" }, { "name": "Preventative Maintenance | Tasks" }, { "name": "HCM | UKG Pay Deductions" }, { "name": "HCM | UKG Pay Earnings" }, { "name": "HCM | UKG Pay Headers" }, { "name": "HCM | UKG Pay Taxes" }, { "name": "HCM | Payroll Geographical States" }, { "name": "HCM | Payroll Trades" }, { "name": "HCM | Payroll Union" }, { "name": "HCM | Payroll Pay Runs" }, { "name": "HCM | Payroll Pay Groups" }, { "name": "HCM | Payroll Tax" }, { "name": "HCM | Payroll Worker Compensation" }, { "name": "HCM | Payroll Work Locations" }, { "name": "HCM | Payroll Trade Pay Rates" }, { "name": "HCM | Payroll Union Pay Rates" }, { "name": "HCM | Payroll Job Pay Rates" }, { "name": "HCM | Payroll Master Benefits" }, { "name": "HCM | Payroll Master Deductions" }, { "name": "HCM | Payroll Ben/Ded/Leave Base Codes" }, { "name": "HCM | Payroll Ben/Ded Plans" }, { "name": "HCM | Payroll Ben/Ded Plan Options" }, { "name": "HCM | Payroll Company Benefits" }, { "name": "HCM | Payroll Company Deductions" }, { "name": "HCM | Payroll Vertex Geographic Locations" }, { "name": "HCM | Payroll Checks" }, { "name": "HCM | Payroll Timesheets" }, { "name": "HCM | Employee" }, { "name": "HCM | Employee (Minimum payload)" }, { "name": "HCM | Employee History" }, { "name": "HCM | Tax Exemptions" }, { "name": "HCM | Employee Tax Overrides" }, { "name": "HCM | Employee Pay Splits" }, { "name": "HCM | Employee Benefits" }, { "name": "HCM | Employee Clock In and Out" }, { "name": "HCM | Employee Deductions" }, { "name": "HCM | Employee Leaves" }, { "name": "HCM | Employee Leave History" }, { "name": "HCM | Employee Hour Types" }, { "name": "HCM | Employee Pay History" }, { "name": "HCM | Employee Work Statuses" }, { "name": "HCM | Employee Security Group" }, { "name": "HCM | Crewtime Crew" }, { "name": "HCM | Crewtime Employee Timesheet" }, { "name": "HCM | Crewtime Equipment Timesheet" }, { "name": "HCM | Crew Maintenance Activity Assignment" }, { "name": "HCM | Crew Maintenance Member Assignment" }, { "name": "HCM | Crew Maintenance Member Trade and Union Assignment" }, { "name": "HCM | Crew Maintenance Equipment Assignment" }, { "name": "HCM | Crew Maintenance Equipment Detail Assignment" }, { "name": "HCM | HR Requisitions" }, { "name": "HCM | HR Relations" }, { "name": "HCM | HR Employee Skills" }, { "name": "HCM | HR Incident" }, { "name": "HCM | HR Employee Relatives / Dependents" }, { "name": "HCM | HR Employee Positions" }, { "name": "HCM | HR Applicants" }, { "name": "HCM | HR Applications" }, { "name": "HCM | Vertex Location City" }, { "name": "HCM | HR Application History" }, { "name": "HCM | HR Dependent Benefits" }, { "name": "HCM | HR Dependent Deductions" }, { "name": "HCM | HR Employee Elected Plans" }, { "name": "HCM | HR Employee Training Certifications" }, { "name": "HCM | HR Trainings" }, { "name": "HCM | E-Timesheets" }, { "name": "HCM | System Contacts" }, { "name": "HCM | System User Payroll Security Group" }, { "name": "HCM | Payroll Timesheet Posting" }, { "name": "HCM | CrewTimesheet Posting" }, { "name": "HCM | HR Positions Master" }, { "name": "HCM | Payroll Pay Periods" }, { "name": "HCM | Payroll Rate Codes" }, { "name": "HCM | Payroll Overhead Codes and Rates" }, { "name": "HCM | Payroll Assigned Overhead to Jobs" }, { "name": "Materials Management | Material Sale Orders" }, { "name": "Materials Management | Material Sale Orders Details" }, { "name": "Materials Management | Truck Rate Detail" }, { "name": "Opportunity Management | Competitors" }, { "name": "Opportunity Management | Opportunities" }, { "name": "Opportunity Management | Revenue Details" }, { "name": "Opportunity Management | Opportunity History" }, { "name": "Opportunity Management | Organization" }, { "name": "Project Controls | Job Billing" }, { "name": "Project Controls | Job Cost" }, { "name": "Project Controls | PCI Details" }, { "name": "Project Controls | Unposted PCI Details" }, { "name": "Project Controls | PCI Headers" }, { "name": "Project Controls | Owner Change Orders" }, { "name": "Project Controls | CM Statuses" }, { "name": "Project Controls | CM Types" }, { "name": "Project Controls | CM Vendor Details" }, { "name": "Project Controls | Post PCI" }, { "name": "Project Management | Uploading Documents" }, { "name": "Project Management | Downloading Documents" }, { "name": "Project Management | Foreign Bid Item Imports" }, { "name": "Project Management | Communications" }, { "name": "Project Management | Daily Journals" }, { "name": "Project Management | Communications Types" }, { "name": "Project Management | Daily Journal Daily Work Plans" }, { "name": "Project Management | Daily Journal Field Forces" }, { "name": "Project Management | Daily Journal Labour" }, { "name": "Project Management | Daily Journal Materials" }, { "name": "Project Management | Daily Journal Owner Equipment" }, { "name": "Project Management | Daily Journal Quality Control" }, { "name": "Project Management | Daily Journal Tasks" }, { "name": "Project Management | Daily Journal Trade Equipment" }, { "name": "Project Management | Daily Journal Transactions" }, { "name": "Project Management | Daily Journal User Defined Data" }, { "name": "Project Management | Daily Journal Visitors" }, { "name": "Project Management | Daily Journal Bill Details" }, { "name": "Project Management | Field Work Directives" }, { "name": "Project Management | Contract Types" }, { "name": "Project Management | Company Contacts" }, { "name": "Project Management | Distribution BCC" }, { "name": "Project Management | Distribution CC" }, { "name": "Project Management | Field Work Directive Statuses" }, { "name": "Project Management | Issues" }, { "name": "Project Management | Key Players" }, { "name": "Project Management | Meetings" }, { "name": "Project Management | Meeting Attendees" }, { "name": "Project Management | Meeting Item Statuses" }, { "name": "Project Management | Meeting Tracks" }, { "name": "Project Management | Notes" }, { "name": "Project Management | Projects" }, { "name": "Project Management | Project Items" }, { "name": "Project Management | Project Item Phase Segment Sums" }, { "name": "Project Management | Project Partners" }, { "name": "Project Management | Notices" }, { "name": "Project Management | Notice Statuses" }, { "name": "Project Management | Owner JS Query" }, { "name": "Project Management | PCI Real Locations" }, { "name": "Project Management | Project Contacts" }, { "name": "Project Management | RFIs (Requests for Information)" }, { "name": "Project Management | RFI Statuses" }, { "name": "Project Management | Submittal Packages" }, { "name": "Project Management | Submittal Package Details" }, { "name": "Project Management | Submittal Package Status" }, { "name": "Project Management | Submittals" }, { "name": "Project Management | Submittal Status" }, { "name": "Project Management | Transmittals" }, { "name": "Project Management | Subcontract Headers" }, { "name": "Project Management | Subcontract Schedules" }, { "name": "Project Management | Subcontract Sechedule Phase Segment Sums" }, { "name": "Project Management | User Roles" }, { "name": "Project Management | Punchlists" }, { "name": "Project Management | Punchlist Details" }, { "name": "Project Management | Punchlist Statuses" }, { "name": "Project Management | Meeting Items" }, { "name": "Project Management | Self Perform Vendor" }, { "name": "Project Management | Submittal Types" }, { "name": "Project Management | Assign contact and partner to project" }, { "name": "Project Management | Subcontract Prequal" }, { "name": "Project Management | Bid Item Package" } ], "paths": { "/sys-rest-api/jersey/v1/user-defined-fields": { "get": { "tags": [ "Core System | User-defined-fields" ], "summary": "getUdfData", "description": "# GET /jersey/v1/user-defined-fields — Get UDF Field Values\n\n## Overview\n\nThis endpoint returns all user-defined field (UDF) labels, their physical column names, and the current stored values for a specific record. You identify the record by passing the table name and its business keys. The endpoint works for any UDF-enabled table in CMiC — Projects, Jobs, Vendors, Cost Items, and so on — without any object-specific code.\n\n| Property | Value |\n| --- | --- |\n| URL | `{base_url}/sys-rest-api/jersey/v1/user-defined-fields` |\n| Method | `GET` |\n| Produces | `application/json` |\n| Success Status | `200 OK` |\n| Auth | Basic (`Authorization: Basic {credentials}`) |\n\n---\n\n## Notes\n\nAuthentication and authorization are required for all calls.\n\n`schemaName` defaults to `DA` if not supplied. You only need to pass it if you are working in a different schema.\n\n`objectKey1` is always required. Additional keys (`objectKey2` through `objectKey10`) are only needed when the table uses a composite key — for example, a Cost Item needs both Company Code and Item Code.\n\nIf the parent record does not exist in the database, the endpoint returns a 400 error. If no UDF definition exists for the table, it also returns a 400. The response will include an error code and a human-readable message in both cases.\n\nAudit columns (`createDate`, `createUser`, `updateDate`, `updateUser`) are populated from the UDF value row itself, not from the parent table.\n\n---\n\n## UI Navigation\n\nUser-defined fields are custom fields that are attached directly to the object they belong to. They appear on the object's own screen — there is no separate standalone navigation path for them. For example, UDFs for a Project appear on the Project record itself, and UDFs for a Job appear on the Job record. \n\n---\n\n## Finders\n\nThe following finders are available to identify and retrieve a specific record.\n\nThis endpoint always returns a single record. There is no list mode — you must supply enough key information to identify exactly one parent record. The combination of `tableName` and the business keys is what acts as the finder.\n\n| Finder Parameter | Required | How It Narrows the Result |\n| --- | --- | --- |\n| `tableName` | Yes | Tells the endpoint which UDF-enabled table to look in (e.g. `PROJ`, `JCJOB`, `CIITEM`, `JCCOST`). Every call must include this. |\n| `objectKey1` | Yes | The first (and often only) business key of the parent record. For a Project this would be the Company Code. For a single-key table this alone identifies the record. |\n| `objectKey2` | Depends | Required when the table uses a composite key. For a Project, this would be the Project Number. For a Cost Item, the Item Code. |\n| `objectKey3` through `objectKey10` | Depends | Only needed for objects with three or more key parts. Most objects use one or two keys. Pass `null` or omit any slot you do not need. |\n| `schemaName` | No | Defaults to `DA`. Only supply this if your data lives in a different schema. |\n\n**Single-key example** — retrieve UDFs for Job `JOB-001` in company `01`:\n\n```\nGET .../v1/user-defined-fields?tableName=JCJOB&objectKey1=01&objectKey2=JOB-001\n\n ```\n\n**Composite-key example** — retrieve UDFs for Cost Item `BOLT-123` in company `01`:\n\n```\nGET .../v1/user-defined-fields?tableName=CIITEM&objectKey1=01&objectKey2=BOLT-123\n\n ```\n\nIf you are unsure what `objectKey1` and `objectKey2` mean for a given table, call the definition endpoint first:\n\n```\nGET .../v1/user-defined-fields/definition?tableCode=CIITEM_K\n\n ```\n\nThat tells you the label for each key slot before you make the data call.\n\n---\n\n## Query Standards\n\n| Key | Description |\n| --- | --- |\n| `tableName` | Required. Identifies which UDF-enabled table to query. |\n| `objectKey1` | Required. First part of the business key that uniquely identifies the parent record. |\n| `objectKey2` through `objectKey10` | Optional. Additional key parts for composite-key tables. Unused slots can be omitted. |\n| `schemaName` | Optional. Database schema. Defaults to `DA`. |\n\n---\n\n## Attributes\n\n### Response — Top Level\n\n| Field | Type | Description | Example |\n| --- | --- | --- | --- |\n| `schemaName` | String | Schema that owns the table | `DA` |\n| `tableName` | String | Table the UDFs belong to | `PROJ` |\n| `objectKey1` | String | First business key value | `MAIN` |\n| `objectKey2` through `objectKey10` | String | Remaining key values (null if unused) | `P001` |\n| `objectKeyName1` | String | Column name behind objectKey1 | `PROJ_COMP_CODE` |\n| `objectKeyName2` through `objectKeyName10` | String | Column names behind remaining keys (null if unused) | `PROJ_NUM` |\n| `fieldCount` | Integer | Number of UDF fields returned | `5` |\n| `createDate` | String (ISO 8601) | Date the UDF value row was first created | `2025-03-10T09:00:00-04:00` |\n| `createUser` | String | User who created the UDF value row | `JSMITH` |\n| `updateDate` | String (ISO 8601) | Date the UDF value row was last updated | `2026-06-01T14:22:00-04:00` |\n| `updateUser` | String | User who last updated the UDF value row | `BWILSON` |\n| `fields` | Array | List of UDF field entries — see below | |\n\n### Response — fields\\[\\] Array\n\n| Field | Type | Description | Example |\n| --- | --- | --- | --- |\n| `fieldName` | String | Human-readable label configured for this UDF slot | `Project Category` |\n| `columnName` | String | Physical column name in the UDF value table | `UEV_CODE1` |\n| `value` | String | Current stored value. `null` if nothing has been saved yet | `COMMERCIAL` |\n\n---\n\n## Example\n\n### Request\n\n```\nGET {base_url}/sys-rest-api/jersey/v1/user-defined-fields\n ?tableName=PROJ&objectKey1=MAIN&objectKey2=P001\nAuthorization: Basic {credentials}\n\n ```\n\n### Response — 200 OK\n\n```\n{\n \"schemaName\": \"DA\",\n \"tableName\": \"PROJ\",\n \"objectKey1\": \"MAIN\",\n \"objectKey2\": \"P001\",\n \"objectKey3\": null,\n \"objectKey4\": null,\n \"objectKey5\": null,\n \"objectKey6\": null,\n \"objectKey7\": null,\n \"objectKey8\": null,\n \"objectKey9\": null,\n \"objectKey10\": null,\n \"objectKeyName1\": \"PROJ_COMP_CODE\",\n \"objectKeyName2\": \"PROJ_NUM\",\n \"objectKeyName3\": null,\n \"createDate\": \"2025-03-10T09:00:00-04:00\",\n \"createUser\": \"JSMITH\",\n \"updateDate\": \"2026-06-01T14:22:00-04:00\",\n \"updateUser\": \"BWILSON\",\n \"fieldCount\": 3,\n \"fields\": [\n { \"fieldName\": \"Project Category\", \"columnName\": \"UEV_CODE1\", \"value\": \"COMMERCIAL\" },\n { \"fieldName\": \"Budget Flag\", \"columnName\": \"UEV_CODE2\", \"value\": \"Y\" },\n { \"fieldName\": \"Review Date\", \"columnName\": \"UEV_DATE1\", \"value\": null }\n ]\n}\n\n ```\n\n---\n\n## Error Codes\n\n| HTTP | Error Code | Reason |\n| --- | --- | --- |\n| 400 | `SD-000375-ERR` | `tableName` or `objectKey1` was not provided |\n| 400 | `SD-000376-ERR` | Parent record not found for the supplied keys |\n| 400 | `SD-000377-ERR` | No UDF definition exists for this table |\n| 500 | — | Unhandled database or server error |", "parameters": [ { "name": "schemaName", "in": "query", "schema": { "type": "string" }, "example": "DA" }, { "name": "tableName", "in": "query", "schema": { "type": "string" }, "example": "POMAST" }, { "name": "objectKey1", "in": "query", "schema": { "type": "string" }, "example": "ZZ" }, { "name": "objectKey2", "in": "query", "schema": { "type": "string" }, "example": "PZZ0000106" }, { "name": "objectKey3", "in": "query", "schema": { "type": "integer" }, "example": "1" } ], "responses": { "200": { "description": "OK", "headers": { "Content-Type": { "schema": { "type": "string", "example": "application/json" } } }, "content": { "text/plain": { "schema": { "type": "string" }, "example": "{\n \"schemaName\": \"DA\",\n \"tableName\": \"POMAST\",\n \"createDate\": \"2025-12-02T12:40:04-05:00\",\n \"createUser\": \"SHAHIDWS\",\n \"updateDate\": \"2026-06-16T20:29:17-04:00\",\n \"updateUser\": \"YASHB\",\n \"objectKey1\": \"ZZ\",\n \"objectKey2\": \"PZZ0000106\",\n \"objectKey3\": \"1\",\n \"objectKey4\": null,\n \"objectKey5\": null,\n \"objectKey6\": null,\n \"objectKey7\": null,\n \"objectKey8\": null,\n \"objectKey9\": null,\n \"objectKey10\": null,\n \"objectKeyName1\": \"POMST_COMP_CODE\",\n \"objectKeyName2\": \"POMST_NUM\",\n \"objectKeyName3\": \"POMST_RELEASE_NUM\",\n \"objectKeyName4\": null,\n \"objectKeyName5\": null,\n \"objectKeyName6\": null,\n \"objectKeyName7\": null,\n \"objectKeyName8\": null,\n \"objectKeyName9\": null,\n \"objectKeyName10\": null,\n \"fieldCount\": 4,\n \"fields\": [\n {\n \"fieldName\": \"APITEST\",\n \"columnName\": \"UEV_CODE1\",\n \"value\": \"YashBhavsar\"\n },\n {\n \"fieldName\": \"REMARKS1\",\n \"columnName\": \"UEV_CODE2\",\n \"value\": \"Hello243\"\n },\n {\n \"fieldName\": \"NEWNAMES\",\n \"columnName\": \"UEV_CODE3\",\n \"value\": \"New1NameYash\"\n },\n {\n \"fieldName\": \"REMARKS2\",\n \"columnName\": \"UEV_CODE4\",\n \"value\": \"Rijoe\"\n }\n ]\n}" } } } } } } }, "components": { "securitySchemes": { "cmicBasicAuth": { "type": "http", "scheme": "basic", "description": "Basic authentication" } } } } ````