tags format in CSV upload
ART-2575_KNOWLEDGE_NODE-29
Tags\n\nEnsure all tags listed in the CSV file already exist within the application. Tags are not created automatically during the import process to prevent errors and maintain control. For example, if your CSV contains a tag in the tags.name column such as Q3FY25\\_CSS\\_Forum\\_Bay\\_Area, ensure to create the tag in the system first.\n\n### Owner fields\n\nFor accounts, owner information must be provided in email format. Avoid using names or display names.\n\nLimitations\n-----------\n\nThe
Account and contact import | Computer for Growth Teams | DevRev
ART-15689_KNOWLEDGE_NODE-26
and must contain a valid work item display ID.\n2. For tagging users in the timeline entries, use the format <user@email.com>.\n3. Timeline entries can be added to both internal discussions and customer messages.\n4. The CSV should contain at least one of internal\\_discussion or external\\_discussion columns.\n\n![]()\n\nThe maximum row limit for the input CSV is 5,000.\n\nValidations for uploading CSV\n-----------------------------\n\nThe following validations are done while creating timeline
CSV comments uploader | Automate | Snap-ins | DevRev
ART-2010_KNOWLEDGE_NODE-25
from a CSV file. The CSV file supports the following columns:\n\n```\n```\n1 Title,Description,Owners,Part,Tags,Subtype,WorkType\n\n\n\n2 Front page not loading,"This is a sample ticket body with \xe2\x80\x9c\xe2\x80\x9d quotes",youremail@example.com,PROD-1,frontend,subtype1,Ticket\n\n\n\n3 APIs returning errors,"The user.get API is returning 500",youremail@example.com,PROD-2,backend,subtype2,Issue\n```\n```\n\nThe Title column is required, while the others are optional. If the WorkType column
Bulk work item uploader | Automate | Snap-ins | DevRev
ART-16355_KNOWLEDGE_NODE-26
**Reported\\_by,** and **Contact** columns, provide the email of the person to be assigned as the owner or reporter of the work item. If the CSV lists multiple owners, only the first will be set as the owner.\n* For the **Applies to Part**, **Stage**, **Account**, **Developed with Parts**, and **Tags** columns, provide the part name, stage name, account name, part name, and tag name respectively as it is present in the UI, ensuring case sensitivity.\n* For **Date** and **Timestamp** related
CSV commands uploader | Automate | Snap-ins | DevRev
ART-4022_KNOWLEDGE_NODE-27
person who should be assigned as the owner or reporter of the work item. If the CSV lists multiple owners, only the first is set as the owner.\n2. For Applies to Part, Stage, Account, RevOrg, Developed with Parts, and Tags columns, provide the part name, stage name, account name, workspace, part name, and tag name respectively as it appears in the UI (case-sensitive).\n3. For Date and Timestamp related fields, provide the date and timestamp in the format YYYY/MM/DD.\n4. The tnt\\_\\_ prefix in
CSV work item uploader | Automate | Snap-ins | DevRev
ART-2575_KNOWLEDGE_NODE-28
a database identifier or an email address.)\n* account\\_external\\_reference (the external reference of the contact\'s parent account)\n\n### Array fields\n\nFor fields that accept multiple values, such as **owners** and **industry**, values should be separated by commas (,). For example, Agriculture and Forestry should be written as Agriculture,Forestry.\n\n![]()\n\nIf a value contains a comma, enclose it in backticks. For example, enter "Rail, Bus & Taxi" as `Rail, Bus & Taxi`.\n\n###
Account and contact import | Computer for Growth Teams | DevRev
ART-17228_KNOWLEDGE_NODE-7
"tags": ["bug", "good-first-issue"] |\n| 15 | } |\n```\n\nSome systems provide collections as enum values or references in a string, separated by some separator (comma or semicolon):\n\n```\n|  |  |\n| --- | --- |\n| 1 | { |\n| 2 | "reporter_ids": "2103232131,2103232144", |\n| 3 | "tags": "bug;good-first-issue" |\n| 4 | } |\n```\n\nThis format should be avoided, and the data normalized to the natural format in the extractor.\n\n###### Using struct fields\n\nStructs are embedded JSON objects
Common issues | DevRev | Docs
ART-17221_KNOWLEDGE_NODE-12
provides values such as "", \xe2\x80\x931 for missing values,\n  those must be set to null.\n* Timestamps: Full-precision timestamps should be formatted as RFC3339 (`1972-03-29T22:04:47+01:00`),\n  and dates should be just `2020-12-31`.\n* References: references must be strings, not numbers or objects.\n* Number fields must be valid JSON numbers (not strings).\n* Multiselect fields must be provided as an array (not CSV).\n\nExtracted items are automatically normalized when pushed to the `repo`
Data extraction | DevRev | Docs
ART-17231_KNOWLEDGE_NODE-141
`tag`\n\n**Capabilities:** Can Load\n\n### Fields\n\n| Field | Type | Required | Description |\n| --- | --- | --- | --- |\n| `access_level` | enum |  | Access level for the tag |\n| `created_by_id` | reference\xe2\x86\x92[#category:user] |  | User ID of the user that created the object |\n| `description` | rich\\_text |  | Description of the tag |\n| `name` | text | \xe2\x9c\x94\xef\xb8\x8e | Name of the tag |\n| `style` | text |  | hex color of in the format #RRGGBB |\n\n#### Enum
Supported DevRev object types | DevRev | Docs
ART-6175_KNOWLEDGE_NODE-30
generated account description.\n  **Example:**\n\n  ```\n  ```\n  1 Name, DOB, Address\n  ```\n  ```\n* **Account Tags:**\n  Provide a comma-separated list of tags to apply to newly created accounts.\n  **Example:**\n\n  ```\n  ```\n  1 is_followup, immutable\n  ```\n  ```\n* **Airtable to Contact Mapping:**\n  Map Airtable fields to DevRev *Contact* object fields.  \n  Do not include email or phone here\xe2\x80\x94they\'re handled.\n  **Format:**\n\n  ```\n  ```\n  1 { "<Airtable Column
Airtable | Automate | Snap-ins | DevRev
ART-6177_KNOWLEDGE_NODE-34
**Example:**\n\n  ```\n  ```\n  1 { "tnt__source": "Tracxn", "tnt__verified": "true" }\n  ```\n  ```\n* ***Contact* Tags:**  \n  Comma-separated list of tags to apply to newly created *Contacts*.\n\n  **Example:**\n\n  ```\n  ```\n  1 founder, outreach-target\n  ```\n  ```\n* ***Contact* Owner Mapping:**  \n  Dynamically assign ownership of *Contacts* based on email.\n\n  **Format:**\n\n  ```\n  ```\n  1 { "<Owner Email>": "<Custom Field API Name>" }\n  ```\n  ```\n\n  **Example:**\n\n  ```\n
Tracxn sync | Automate | Snap-ins | DevRev