I have a CRM that I am moving away from that has knowledgebase articles in XML format that I want to import into EspoCRM and Comments from a ticketing system that I want to import to EspoCRM. Does anyone have an easy way to accomplish both of these imports?
Import Help
Collapse
X
-
Tags: None
-
Hi nocstaff@urbancom.net,
To allow import of notes in EspoCRM, you need to specify the following in the {ESPO_DIR}/custom/Espo/Custom/Resources/metadata/scopes/Note.json file:
Code:{ "importable": true }
- the parent type is specified (e.g., Case or Ticket)
- the parent ID is specified
- the note type is specified as Post
Last edited by lazovic; Yesterday, 08:39 AM. -
Thank you for responding back. I went to /var/www/espocrm/data/espocrm/custom/Espo/Custom/Resources/metadata/scopes and only saw a SMS.json file. I created a Note.json file and added
{
"importable": true
}
I cleared cache and did a rebuild. I went back to import the csv and when mapping notes I do not see Post as an optionComment
-
Comment
-
-
-
-
-
nocstaff@urbancom.net,
So you have selected the wrong entity for import. There should be a Note entity in Step 1 of import.
Also, keep in mind that you need to select the type in the Default Values panel:
Comment
-
Ok before I do this, how do I associate the notes with each case then? I already imported all of the cases without the notes for each caseComment
-
nocstaff@urbancom.net,
It all depends on what fields are in your CSV file. Workflow should be able to relate specific notes to specific tickets/cases.Comment
-
I went and selected Notes instead of Cases in the entity type in step 1, and now as you said, I am able to select Post as an option in Default value in step 2. I'm still a little confused about how to match the comments with the correct cases, however. I included 2 screenshots of what my csv table headers look like. Do I have to add a different row to this file in order to make it work, or can I just use my pre existing headers? I'm not certain what fields needs to be filled in here.Comment
Comment