delete customer field from custom fields in issue
ART-15487_KNOWLEDGE_NODE-23
and chain the fragments.\n\n##### \n\nYou want to add a new boolean field *customer\\_impact* to the *bug* subtype\nand delete the *regression* field.\n\nThe API call to add the new field and delete the old field is shown below:\n\n```\n|  |  |\n| --- | --- |\n| $ | curl --location \'https://api.devrev.ai/schemas.custom.set\' \\ |\n| > | --header \'Content-Type: application/json\' \\ |\n| > | --header \'Authorization: Bearer <TOKEN>\' \\ |\n| > | --data \'{ |\n| > | "type":
Object customization | DevRev | Docs
ART-1957_KNOWLEDGE_NODE-34
on the field.\n   * **Description**: Add some information about why you added this field. This is only visible to you.\n3. Click **Save to draft**. These fields can be reviewed and then published by clicking **Publish changes**.\n4. Review the changes and click **Publish changes** once you are ready.\n5. Refresh the page to see the changes in published mode. You can\'t make changes in this mode.\n\nTo edit or delete a custom field, click the **\xe2\x8b\xae** icon next to the field. You\'ll see
Object customization | Computer by DevRev | DevRev
ART-1645_KNOWLEDGE_NODE-28
{  \n    >|             "name": "customer_impact",  \n    >|             "field_type": "bool",  \n    >|             "is_filterable": true,  \n    >|             "ui": {  \n    >|                 "display_name": "Customer Impact",  \n    >|             }  \n    >|         }  \n    >|     ],  \n    >|     "deleted_fields": [ "regression" ]  \n    >| }\'\n[/code]  \n  \nNote that:\n\n  * The API payload reflects the entire state of the new fragment version.\n  * The `deleted_fields` array
Object customization (Beta) — DevRev | Docs
ART-1645_KNOWLEDGE_NODE-25
older fragment are unaffected (more on this later).\n\nThe same API endpoint `schemas.custom.set` is used to create and update fragments. The API internally figures out how to version and chain the fragments.\n\n#####\n\nYou want to add a new boolean field _customer_impact_ to the _bug_ subtype and delete the _regression_ field.\n\nThe API call to add the new field and delete the old field is shown below:\n\n[code]\n\n    $| curl --location \'https://api.devrev.ai/schemas.custom.set\' \\  \n
Object customization (Beta) — DevRev | Docs
ART-15487_KNOWLEDGE_NODE-25
"field_type": "rich_text", |\n| > | "ui": { |\n| > | "display_name": "RCA", |\n| > | } |\n| > | }, |\n| > | { |\n| > | "name": "customer_impact", |\n| > | "field_type": "bool", |\n| > | "is_filterable": true, |\n| > | "ui": { |\n| > | "display_name": "Customer Impact", |\n| > | } |\n| > | } |\n| > | ], |\n| > | "deleted_fields": [ "regression" ] |\n| > | }\' |\n```\n\nNote that:\n\n* The API payload reflects the entire state of the new fragment version.\n* The `deleted_fields` array specifies
Object customization | DevRev | Docs
ART-1645_KNOWLEDGE_NODE-29
specifies the field names that are being deleted. If not provided, the API call fails due to the lack of an explicit field deletion confirmation. This prevents accidental field deletions.\n\nThe above API call internally performs the following steps:\n\n  1. Creates a new fragment with the specified payload.\n  2. Updates the new fragment to point to the previous fragment. The `old_fragment_ref` system field in the new fragment points to the previous fragment.\n  3. Updates the old fragment to
Object customization (Beta) — DevRev | Docs
ART-1957_KNOWLEDGE_NODE-35
two options: **Edit** and **Delete**. Click **Edit** to enter edit mode and make changes. This mode displays all the recent changes you have made. Changes persist locally, meaning they will remain as you navigate around the app.\nHowever, if you refresh or close and reopen the app, these changes will vanish. If you choose to delete the field, ensure you won\'t lose any important data before proceeding.\n\n![]()\n\nAdd a new subtype\n-----------------\n\nYou can add a new subtype to an existing
Object customization | Computer by DevRev | DevRev
ART-15716_KNOWLEDGE_NODE-31
conditions While creating custom schema\n\nThis can be handled by our team. Kindly reach out to us, and we\xe2\x80\x99ll be happy to assist you with setting up a custom schema. Would you like us to create a ticket for this?\n\nAPI for stage customizationThis can be handled by our team. Kindly reach out to us, and we\xe2\x80\x99ll be happy to assist you with setting this up. Would you like us to create a ticket for this?\n\nStage customization (e.g., customizing workflow stages for tickets,
Support queries related playbook