DocBits- IDP for Infor ERP
HomeAppStatusAPI
🇺🇸 English
🇺🇸 English
  • Overview and Basics
    • DocBits
      • Key Features of DocBits
    • Architecture
      • DocBits Infor on Premise Customer
      • Certifications
    • Infor Infrastructure
    • Release Notes
      • Testing Availability on Sandbox
    • FAQ
      • General Information
      • Document Processing
        • Table Extraction Troubleshoot
      • Infor LN (LN Integration)
        • Export Error: "Error Exporting Document to LN. Status Code: 500"
          • not found in direct debit
          • Request validation; Attr. 'ReceiptLine', Value " " : the value must be numeric.
      • Infor M3 (M3 Integration)
        • Costing elements are not properly configured. Please ask your admin to configure it.
      • Mandatory PDP/PPF Channels – PEPPOL as Transport Only for France’s 2026 E-Invoicing
  • End User and Partner Section
    • End User Section
      • Dashboard
        • Dashboard Tools
        • Document Merging
        • Document Status
        • Filtering Documents
        • Overview of Uploaded Documents
        • Task Counter
        • Validated Extracted Fields
        • Document Flow
        • Troubleshooting
        • Keyboard Shortcuts
      • Tasks
      • Advance Shipment Dashboard
      • Purchase Order Dashboard
      • Invoice Dashboard
      • Shipment Order Dashboard
      • User Configuration Options
      • AI Table
        • AI Table Tags
      • Validation Screen
        • Fuzzy Data
        • QR Codes
        • Keyboard Shortcuts
      • Purpose and Use
      • Purchase Order Matching
        • Purchase Order Matching Tools
        • Rules and Calculations
        • Automatic Purchase Order Data Matching
        • Supplier Item Number Map
        • Keyboard Shortcuts
      • Accounting for Cost Invoice and Indirect Sales
      • How to Import Documents
        • FTP
        • Manual Import
        • Webhook
        • Email
          • IMAP
          • OAuth Office365
      • Technical Support in DocBits
        • Create a ticket
        • Help Icons
      • Course
        • Introduction
        • Dashboard
        • Validated Documents
        • AI Table
        • Master PO Matching with DocBits
      • Our Document Priority System
      • Supplier Portal
        • Supplier Registration
        • Supplier Satuts
      • Ressources and Support
        • User Support
    • Partner Section
      • Invoice Automation Testing with DocBits
  • Administration and Setup
    • Settings
      • Global Settings
        • Company Information
          • Defining App Color in Company Settings
        • Groups, Users and Permissions
          • Users
            • Modifying User Details
            • Admin Privileges
          • Sub-Organizations
            • How to create a Sub-Organization
          • Groups and Permissions
            • Purpose and Use
            • Adding/Editing Groups
            • Activating Permissions
            • Access Control
            • Troubleshooting
        • Integration
          • API Key
          • API Calls and Examples
          • API Key Management
          • Configuring Single Sign-On (SSO)
            • Infor SSO Configuration
              • V1
              • V2
              • Azure SSO
          • Identity Service Provider Configuration
          • Best practices
          • Troubleshooting Common Issues
        • Document Types
          • Purpose and Scope
          • Adding/Editing Document Types
          • Activation
          • Customization Options
          • Best Practice
          • Troubleshooting
          • Layout Manager
            • Purpose and Use
            • Navigating the Layout Manager
            • Configuring Field Properties
            • Using the Template Preview
            • Save and apply changes
            • Best practices
            • Troubleshooting
          • Document Sub Types
          • Creating a new Sub Type
          • Configure subtypes
          • Using Actions
          • Best Practices
          • Table Columns
            • Purpose and Use
            • Adding a new Column
            • Editing and deleting columns
            • Best practices
            • Troubleshooting
          • Fields
            • Purpose and Use
            • Adding and Editing Fields
            • Configuring Field Properties
            • Setting Validation and Match Score
            • Best practices
            • Troubleshooting
            • New Fields with Charges
          • Model Training
            • Purpose and Use: Model Training
            • Import Data: Model Training
            • Manage training data
            • Testing the model
            • Best practices
            • Troubleshooting
          • Regex
            • Purpose and use
            • Creating a Regex Pattern
            • Editing and Saving Regex Patterns
            • Best practices
            • Troubleshooting
          • Script
          • Script Activation and Management
          • Testing Scripts
          • Purpose and Use
          • Creating and Editing Scripts
          • Best Practices
          • Troubleshooting
          • e-docs
            • Currently Supported E-Invoice Standards
              • Roadmap
            • E-Invoice examples
              • XRechnung 1.2
              • XRechnung 2.0
              • XRechnung 2.1
              • XRechnung 2.2
              • XRechnung 2.3
              • XRechnung 3.0
              • XRechnung Cross Industry Invoice
              • FacturX
            • EDI
              • Purpose and Use
              • Setting Up EDI Templates
                • EDI Structure descriptor
              • Using the XSLT Editor
                • EDI Videos
              • Previewing EDI Messages
              • Best Practices
              • Troubleshooting
              • EDI 810 (Invoice) Mapping
              • EDI 855 (Purchase Order Acknowledgement) Mapping
              • EDI 850 (Purchase Order) Mapping
              • EDI 856 (Advance Shipment Notice) Mapping
            • XRechnung
              • Standard Preview
              • Mapping XRechnung in DocBits
                • TOML Export
            • Peppol BIS Billing 3.0
              • Transformation file and Mapping
            • Faktura
            • ZUGFeRD 1.0, 2.1 and 2.3
            • eSLOG 1.6 and 2.0
          • More Settings
            • Purpose and use
            • Best practices
            • Troubleshooting
            • Duplicate Detection
            • Approval
              • Approval Stamp
              • Approval History
            • Purchase Order
              • PO Table in Layout Builder
              • Auto check for PO updates
              • Calculate PO unit price
              • Export not matched PO lines
              • Purchase order tolerance settings / Additional purchase order tolerance
              • Purchase order disable statuses
              • Supplier Item Number Map - Admin Documentation
        • Email Notification
          • Configuring Notifications
          • Managing Notifications
          • Best Practice
          • Troubleshooting
        • E-Mail templates
        • Dashboard
          • Customizing Filters
      • Document Processing
        • Documents Expiry
        • Import
          • Test: Multi Email Import and Handling Tests
          • Test: Email Import and Handling Tests
          • Test: FTP Import Connection
          • Test: File Import 1
        • Rule Manager
          • TransactionConfig Pro Template
            • Case 1, 2, 3: Quantity and Unit Price Within Tolerance
            • Case 4, 5: Quantity Within Tolerance, Unit Price Outside Tolerance (Approved)
            • Case 15: Charge Line - Charge Per Unit Outside Tolerance (Rejected)
            • Case 14: Header Charge - Charge Per Unit Outside Tolerance (Approved)
            • Case 12, 13: Header Charge - Charge Per Unit Within Tolerance
            • Charge Per Unit Outside Tolerance (Rejected)
            • Case 14: Charge Line - Charge Per Unit Outside Tolerance (Approved)
            • Charge Per Unit Within Tolerance
            • Case 11b: Quantity Outside Tolerance (Positive Rejected), Unit Price Outside Tolerance (Rejected)
            • Case 10b: Quantity Outside Tolerance (Negative Rejected), Unit Price Outside Tolerance (Rejected)
            • Case 8b, 9b: Quantity Outside Tolerance (Approved), Unit Price Outside Tolerance (Approved)
            • Case 11a: Quantity Outside Tolerance (Positive Rejected), Unit Price Within Tolerance
            • Case 10a: Quantity Outside Tolerance (Negative Rejected), Unit Price Within Tolerance
            • Case 7: Quantity Within Tolerance, Unit Price Outside Tolerance (Positive Rejected)
            • Case 6: Quantity Within Tolerance, Unit Price Outside Negative Tolerance (Rejected)
            • Case 8a, 9a: Quantity Outside Tolerance (Approved), Unit Price Within Tolerance
            • Case 15: Header Charge - Charge Per Unit Outside Tolerance (Rejected)
            • Tax Lines
        • Ocr Settings
        • Classification And Extraction
          • Table extraction for costing element
          • Auto extract tax code
        • Master Data Lookup
        • List Of Values
        • Export
        • Module
          • Annotation Mode
          • Approval Before Export
          • Doc Scan
          • Doc Script
          • IDM ACL Updater
          • Inbound Emails
          • Swiss QR Code
          • Auto Export if PO Matched 100%
          • Export Dashboard Data
          • How to Create Database Access for a Specific Organization User
        • Decision Trees
      • Log Settings
        • Task Management
        • Data Synchronization
      • API Licenses
      • Supplier Setting
        • Supplier General Settings
        • Editing Email Templates
        • Supplier Layout
        • Export Configuration for Supplier Portal for M3
        • Supplier Permissions
      • Cache Management
    • Workflow
      • When
        • Card description
        • Document Type Operation
        • Document Type One of
      • And
        • Compare with Purchase Order
          • Combined Price of Quantity Difference
          • Unit Price Combined with Fields
          • Promised Delivery Date on Purchase Order
          • Order Data in Order Confirmation
          • Confirmed Delivery Date
          • Compare Order Confirmation with Purchase order
          • Tax in document field
          • Any / All Quantity
          • Compare Total Charges
          • Out of Tolerance Unit Price
          • Any / All Unit Price is
          • Item Id on Purchase Order
          • Supplier on Invoice
          • Order Type of Purchase Order
        • Document Field
          • Checkbox is checked
          • Field is
          • Text in Field
          • Compare two Fields with Tolerance
          • Compare two Fields
          • If Country in Field
          • Docfield is
          • Compare Field with tolerances
          • If Country in Field is One of
        • Date & Time
          • Date or Time
          • Today
        • Document
          • Document Type Operation one of
          • Document Operator for Sub-Organizations
          • Document Type
        • Logic
          • Continue with a chance
          • Send HTTPS Request
          • Module active
          • Quoted Item Price
          • Decision Table has Returns
        • Status
          • Single Document Status Condition
          • Document Status Condition List
        • Table
          • Any Value of
          • All Value of
          • Compare values in table
          • Compare In
          • Item Receiving Method
          • Items Have Shelf Life
        • Assignee
          • Assigned User Condition
          • Single Assigned User Condition
          • Assigned Group Condition
          • Single Assigned User Condition
      • Then
        • Document Field
          • Set to
          • Set Checkbox to
          • Invert Checkbox
        • Document
          • Approve the Document
          • Reject the Document
        • Status
          • Change Status to
        • Export
          • Export with Export Configuration
          • Start Export
          • Export with alternate Export
        • Task
          • Create a New Task and assign it to the User
          • Create a New Task and assign it to the Recipient
          • Create a New Task and assign it to the group
          • Create a New Task and assign it to the User in Document Field
          • Assign a Task with Title
          • Create a New Task and assign it to Procurement Group
          • Assign to Procurement Group and Create a Task/Notification
          • Assign Document and Create Task/Notification for Group
          • Assign Document and Create Task/Notification for User
          • Assign Document and Create Task/Notification
        • Table
          • Change Entries with
          • Calculate Columns with
          • Calculate in
        • Assignee
          • Assign user from field
          • Assign document to User
          • Assign document to recipient
          • Assign document to the sub organization
          • Assign document to matching sub organization
          • Assign to group
          • Assign document to procurement group
          • Assign document to
          • Assign Sequentially to User
          • Assign Sequentially to Procurement Group
          • Assign Sequentially to Groups
          • Assign Sequentially to User/Group
        • Action
          • Call Api
          • Run Workflow
          • Send HTTPS request to
          • AI Calculation for Cost Increase Surcharges
      • Workflow Example: Conditional Export Trigger
      • Workflow Documentation
      • Standard Workflow
        • Above Max Amount
        • Cost Invoice - Export
        • Less than Max Amount
        • Purchase Invoice - 2nd Approval Quantity Export
        • Purchase Invoice - 2nd Approval Quantity
        • Purchase Invoice - 2nd Approval Unit Price Export
        • Purchase Invoice - 2nd Approval Unit Price
      • Material Ordering and Processing Workflow
    • Setup
      • Document Types
        • EDI Data Transformation Process
        • Layout Builder
        • Origin Layouts
        • Regex Manager
      • Document Training
        • Training Header Fields
        • Training Line Fields/Table Training
          • Adding New Columns
          • Defining Tables and Columns
          • Advanced Settings
          • Grouping Function
          • Manual Row Selection
          • Mapping Columns
          • Improving Table Extraction with Regex
          • Save and Delete Rules
      • Testing
        • PO Matching
        • Auto Accounting
          • LN
          • M3
      • Supplier Portal
      • WatchDog Installation
    • Report Page
  • Infor Integration and Configuration
    • Importing Master Data
      • Field Mappings
      • LN
        • Auto Accounting
        • Suppliers and Purchase Orders
          • Purchase Order - FAQ
          • Verifying the Logistic Company Setting for Goods Receipt Discrepancies
        • Tax Codes
      • M3
        • Auto Accounting
        • Suppliers and Purchase Orders
        • How to import all suppliers
        • Table Extraction for costing Element
      • Custom Master Data
    • Exporting in DocBits
      • Export Module
      • Alternate Export
    • Exporting to INFOR
      • Creating a BOD Mapping File
      • Creating an IDM Mapping File
      • Creating an ION API Endpoint
      • Creating an ION API File
      • Export to M3 Mapping (API)
      • Exporting to IDM
      • Stream for Cloud Customers
      • Order Confirmation
      • Document Export Mapping
      • M3
        • Example Export M3
        • Handling Charges with Infor M3
        • M3 Configuration
      • LN
        • Example Export LN
          • Configuring the Default Tax Country for Export LN
        • Export Tax Codes to LN
        • LN Configuration
  • Advanced functions and tools
    • Scripting in DocBits
      • Calculating Total Charges Script for Docbits
      • Calculating Total Charges Script for Docbits
      • Delete lines with empty quantity and amount
      • Formatting Export Certificate Reference Numbers Script for Docbits
      • Functions
      • Generating Extended Invoice Numbers Script for Docbits
      • Generating Extended Invoice Numbers Script for Docbits
      • USD as Default Currency
    • Course
      • A Step-by-Step Guide
      • Connect DocBits with Infor SSO
      • Create your Custom App in Infor OS
      • Infor OS with DocBits API Integration
      • M3 Export
      • Sync Flex Dimensions: Infor to DocBits
    • Postman for DocBits
    • Automated Tests Results
      • Email Import
    • SQL Access
    • Importing Supplier and Purchase Order Data into DocBits from CSV Files
    • PowerBI
      • SQL Access
        • Custom classification document
        • Field
        • Document table column
        • Email template
        • Ephesoft PO matching
        • Fellow kv table column rule
        • Group cache
        • Preferences
        • Sales order
        • API credentials
        • public.document_log
        • Auto accounting
        • Document status trigger
        • Document type
        • Documents
        • Document type attributes
        • Document Report
        • Electronic document extraction attributes
        • Lookup field configuration
        • Lookup table
        • Batch instance
        • Document extracted data
        • Document Import log
        • Lookup Configuration
        • Sub document type
        • Document Status alert
        • Inbound Emails
        • Chat Log
        • REST API Lookup Configurations
        • FTP Import Configurations
        • Purchase Order line
        • Receive delivery line
        • Document Script activation status
        • Field validation rules
        • Custom_classification_document_label
        • Training data
        • Tfidf preferences
        • Additional charge costing element
        • PO match tolerance
        • Auto test document
        • Custom classification tag
        • Supplier address
        • Organisation document type
        • Sub Organisation Cache
Powered by GitBook
On this page
  • Spalten
  • Analyse & Beschreibung

Was this helpful?

Edit on GitHub
Export as PDF
  1. Advanced functions and tools
  2. PowerBI
  3. SQL Access

Field

Spalten

  • id: internal

  • org_id: ID to organisation

  • doc_type: DOC Type

  • is_sub_doc_type_field: boolean

  • profile: internal

  • field_name: internal

  • field_type: internal

  • title: internal

  • translation_key: internal

  • hide_label: boolean

  • input_type: internal

  • input_size: internal

  • icon_left: internal

  • icon_right: internal

  • icon_above: internal

  • group_id: internal

  • row_order: integer

  • sort_order: integer

  • fuzzy_name: internal

  • fuzzy_field: internal

  • fuzzy_primary_field: boolean

  • label_align: internal

  • calculation_formula: text

  • clean_field: boolean

  • alphanumeric_field: boolean

  • placeholder: internal

  • coordinates: internal

  • normalized_coordinates: internal

  • threshold: internal

  • reference_point: internal

  • checkbox_group: internal

  • list_of_values: internal

  • enforce_list_of_values: boolean

  • created_by: integer

  • created_on: timestamp with time zone

  • last_modified_on: timestamp with time zone

  • is_deleted: boolean

  • costing_element: internal

  • erp_field_name: internal

Analyse & Beschreibung

# Technical Documentation for `public.field` Table

## Introduction

The `public.field` table appears to be designed to manage metadata and configuration for different fields associated with documents, likely within an insurance domain. Each row in the table seems to represent a specific field configuration, including its type, label, visibility settings, and other properties that dictate how the field should be presented and processed.

## Columns

### id
- **Meaning**: Unique identifier for each field configuration.
- **Role**: Primary key.
- **Typical Contents**: A UUID string that uniquely identifies each entry in the table.

### org_id
- **Meaning**: Identifier for the organization associated with the field configuration.
- **Role**: Foreign key.
- **Typical Contents**: A UUID referencing an organization.

### doc_type
- **Meaning**: Specifies the document type that the field is associated with.
- **Role**: Possibly a foreign key or a categorical identifier.
- **Typical Contents**: A string in the format `INSURANCE_DOCUMENTS_<UUID>` indicating the document type.

### is_sub_doc_type_field
- **Meaning**: Indicates whether the field is a sub-type of the document type.
- **Role**: Technical field.
- **Typical Contents**: Boolean value (True or False).

### profile
- **Meaning**: Potentially defines the profile or scope of the field.
- **Role**: Descriptive field.
- **Typical Contents**: Often empty or a brief text description.

### field_name
- **Meaning**: The internal name of the field.
- **Role**: Descriptive field.
- **Typical Contents**: A string representing the field's name in a technical context (e.g., `Schadennummer`).

### field_type
- **Meaning**: Defines the type of data the field holds.
- **Role**: Descriptive field.
- **Typical Contents**: Descriptive strings like `STRING`, `AMOUNT`.

### title
- **Meaning**: The display title for the field.
- **Role**: Descriptive field.
- **Typical Contents**: Uppercase string used for displaying the field's label.

### translation_key
- **Meaning**: Key for translation into different languages.
- **Role**: Technical field.
- **Typical Contents**: Lowercase string representing the translation key.

### hide_label
- **Meaning**: Indicates if the field's label should be hidden in the UI.
- **Role**: Technical field.
- **Typical Contents**: Boolean value (True or False).

### input_type
- **Meaning**: Specifies the input method for the field.
- **Role**: Descriptive field.
- **Typical Contents**: Can be empty or contain strings defining the input type.

### input_size
- **Meaning**: Determines the size of the input field.
- **Role**: Descriptive field.
- **Typical Contents**: Can be empty or contain strings defining input size.

### icon_left
- **Meaning**: Icon to display on the left side of the field.
- **Role**: Descriptive field.
- **Typical Contents**: Generally empty or contains icon identifiers.

### icon_right
- **Meaning**: Icon to display on the right side of the field.
- **Role**: Descriptive field.
- **Typical Contents**: Generally empty or contains icon identifiers.

### icon_above
- **Meaning**: Icon to display above the field.
- **Role**: Descriptive field.
- **Typical Contents**: Generally empty or contains icon identifiers.

### group_id
- **Meaning**: Identifier for the group of fields to which this field belongs.
- **Role**: Foreign key.
- **Typical Contents**: A UUID referencing a group of fields.

### row_order
- **Meaning**: Determines the order of the field in a list or form.
- **Role**: Technical field.
- **Typical Contents**: Integer indicating the position.

### sort_order
- **Meaning**: Specifies sorting order for the field.
- **Role**: Technical field.
- **Typical Contents**: Integer that defines sorting precedence.

### fuzzy_name
- **Meaning**: An alternate name for fuzzy matching.
- **Role**: Descriptive field.
- **Typical Contents**: Often empty or contains a string for matching purposes.

### fuzzy_field
- **Meaning**: Specifies if the field is used in fuzzy matching.
- **Role**: Descriptive field.
- **Typical Contents**: Generally empty or contains a string.

### fuzzy_primary_field
- **Meaning**: Indicates if this is the primary field for fuzzy matching.
- **Role**: Technical field.
- **Typical Contents**: Boolean value (True or False).

### label_align
- **Meaning**: Alignment setting for the field label.
- **Role**: Descriptive field.
- **Typical Contents**: Often empty or contains alignment information (e.g., left, right, center).

### calculation_formula
- **Meaning**: Formula used for calculations involving the field.
- **Role**: Technical field.
- **Typical Contents**: Text containing a formula or calculation logic.

### clean_field
- **Meaning**: Indicates if the field should be subject to data cleaning.
- **Role**: Technical field.
- **Typical Contents**: Boolean value (True or False).

### alphanumeric_field
- **Meaning**: Specifies if the field should accept only alphanumeric characters.
- **Role**: Technical field.
- **Typical Contents**: Boolean value (True or False).

### placeholder
- **Meaning**: Placeholder text for the input field.
- **Role**: Descriptive field.
- **Typical Contents**: Often empty or contains guiding text.

### coordinates
- **Meaning**: Coordinate data associated with the field.
- **Role**: Descriptive field.
- **Typical Contents**: Generally empty or contains coordinate information.

### normalized_coordinates
- **Meaning**: Normalized version of coordinates for consistency.
- **Role**: Descriptive field.
- **Typical Contents**: Generally empty or contains normalized coordinate data.

### threshold
- **Meaning**: Threshold value related to field validation or processing.
- **Role**: Descriptive field.
- **Typical Contents**: Generally empty or contains threshold values.

### reference_point
- **Meaning**: Reference point used in calculations or positioning.
- **Role**: Descriptive field.
- **Typical Contents**: Often empty or contains reference point data.

### checkbox_group
- **Meaning**: Grouping identifier for checkbox fields.
- **Role**: Descriptive field.
- **Typical Contents**: Generally empty or contains group identifiers.

### list_of_values
- **Meaning**: Specifies a list of allowed values for the field.
- **Role**: Descriptive field.
- **Typical Contents**: Generally empty or contains a list of values.

### enforce_list_of_values
- **Meaning**: Indicates if the list of values should be strictly enforced.
- **Role**: Technical field.
- **Typical Contents**: Boolean value (True or False).

### created_by
- **Meaning**: Identifier for the user who created the field entry.
- **Role**: Descriptive field.
- **Typical Contents**: Integer referencing a user ID.

### created_on
- **Meaning**: Timestamp of when the field was created.
- **Role**: Technical field.
- **Typical Contents**: Date and time in UTC.

### last_modified_on
- **Meaning**: Timestamp of the last modification to the field.
- **Role**: Technical field.
- **Typical Contents**: Date and time in UTC.

### is_deleted
- **Meaning**: Indicates if the field has been marked as deleted.
- **Role**: Technical field.
- **Typical Contents**: Boolean value (True or False).

### costing_element
- **Meaning**: Costing element associated with the field.
- **Role**: Descriptive field.
- **Typical Contents**: Generally empty or contains costing element identifiers.

### erp_field_name
- **Meaning**: Name of the field as used in ERP systems.
- **Role**: Descriptive field.
- **Typical Contents**: Generally empty or contains ERP-specific field names.

This documentation provides a detailed overview of the structure and purpose of each column within the `public.field` table. It serves as a guide for developers to understand the data model and its application in the system.
PreviousCustom classification documentNextDocument table column

Was this helpful?