☁️
Flow IFS Cloud Development Guidelines
  • Flow IFS Cloud Development Guidelines
  • 👶Getting started
    • OData Basics
    • IFS Cloud
    • Terminology
    • Useful Applications
    • IFS documentation
      • IFS API Explorer
      • Entity details
    • Setting up the OData connector
      • Configure connection between Flow Server and IFS Cloud
      • Selecting which configurations are visible in Flow Server
  • 👩‍💻Flow Development with OData
    • Architecture
    • Flow development and distribution strategy
    • Implementation
      • Operations in OData machine steps
      • Missing operations
      • Translations
      • Iteration
      • Join data sets
      • Misc Tips and trix
      • Document / Media Library Management
      • Response status handling
        • Errors from IFS
      • Operation specific notes
        • Set input parameters using flow script
        • Update
        • 🛠️WIP - Create
        • Read
    • Configuration
      • Authentication models
        • Setup Client credential flow
        • 🛠️Setup Password credentials flow
        • 🛠️Setup Authorization code flow
        • 🛠️Setup OpenID flow
        • Obtaining Authentication related URLs from IFS Cloud
      • Projection administration
        • Administrating new projections
        • Administrating updated projections
      • Configuring projections in IFS
        • Custom Entities
        • Custom Projections
        • 🛠️WIP - Query Designer
        • Quick Reports
    • Trigger Flows from IFS Cloud
      • Trigger User Flows via External Navigation Links
      • Trigger Machine Flows via BPA using commands
      • 🛠️Trigger Flow via Event Action
    • Debugging and Testing
      • Aurena debugging
        • Inspect in web browser
        • IFS debug console
      • OData Connector Log
  • 🪄Advanced
    • Custom Request
    • C# usage in the OData connector
      • Different methods
      • Building request
      • 🛠️WIP - Code examples
Powered by GitBook
On this page

Was this helpful?

  1. Flow Development with OData
  2. Implementation
  3. Operation specific notes

Update

PreviousSet input parameters using flow scriptNextWIP - Create

Last updated 1 year ago

Was this helpful?

Optimistic concurrency control

IFS is built to detect if entity has been updated between the time the Flow app has retrieved the data until it's being updated, change tracking. In pre-cloud IFS, developers returned objversion and objid values in modify PL/SQL calls for this purpose.

In OData calls same check can be enforced using entity specific ETag in request headers if-match attribute upon Update operation. value of an entity can only be retrieved by using "Get by key" -operation prior Update operation.

The ETag value returned by IFS is a base64 encoded value of the combination of objid:objversion.

Providing if-match attribute with value *, IFS will dismiss the optimistic concurrency control.

In case you encounter -error In Update operations, provide the if-match header attribute. By providing the ETag as if-match attribute value; IFS will check that entity has not been updated between your clients "Get by key" request and Update operation.

👩‍💻
ETag location in response in Get by key -operation
Using ETag in if-match header attribute
ODP_MISSING_PRECONDITION
ETag