Top Menu

Jump to content
Home
    Modules
      • Projects
      • Activity
      • Work packages
      • Gantt charts
      • Calendars
      • Team planners
      • Boards
      • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.

    • Help and support
    • Upgrade to Enterprise edition
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Enterprise support

    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
    Activity
  • Roadmap
  • Work packages
    Work packages
  • Gantt charts
    Gantt charts
  • Calendars
    Calendars
  • Team planners
    Team planners
  • Boards
    Boards
  • News
  • Forums

Content

General discussion
  1. OpenProject
  2. Forums
  3. General discussion
  4. How to Lock a Field for editing [ Required for API Data POST and PATCH]

How to Lock a Field for editing [ Required for API Data POST and PATCH]

Added by SIddharth L about 1 year ago

Hi All,

I'm feeding data to the Open Project using an API. Sometimes, I will need to fetch the same data and updates might be required. For that, I need a unique identifier. For example, "Subject" is the field that I want to lock, so the user should edit it. Then, I will retrieve and patch the data using the API.
Or possible to create Hidden Field that can used in API ?

Kindly Support to resolve the issue.

My Sample Data of Subject: XX-000-0001, This will never change thought the Task.


Replies (1)

RE: How to Lock a Field for editing [ Required for API Data POST and PATCH] - Added by Matt User about 1 year ago

I am not sure I understand your problem exactly.

But as far as a "hidden field" is concerned: if you create a custom field, it will not show to users until you add it to the form configuration for your work package types (e.g., http://<your OP host>/types/1/edit/form_configuration).

As long as a field can be moved around in that form definition, you can effectively "deactivate" it by dragging it into the grey box with inactive fields to the right. This will also make the field disappear for users, but it certainly is a way to avoid edits happening to the field.

Fields like subject and status cannot be hidden, however.

  • (1 - 1/1)
Loading...