System Admin and Configuration

Get Involved. Join the Conversation.

Topic

    Vivian Tedford
    Importing custom object data to create an incidentAnswered
    Topic posted April 12, 2019 by Vivian TedfordRed Ribbon: 250+ Points 
    88 Views, 3 Comments
    Title:
    Importing custom object data to create an incident
    Summary:
    I am trying to import data into a custom object and have it create an incident during the import
    Content:

    I am only just beginning to use Custom Objects in a large way and I need to understand something about importing data. I created a custom object and it has 32 fields in it. I want to be able to import data into that object and create an incident. But I also want the individual fields to be able to be pulled into a Workspace.

    So I found the article that advised that to be able to show the fields in the workspace, I have to make it a parent object of the incident, not a child. This is counter-intuitive, but that appears to be a fact. I was able to make the fields show up on the incident by doing it this way. 

    But when I try to import some data into that custom object, I can't find a way to make that create an incident. If I choose the Incident from the data record type, it won't let me map to any of the fields in the custom object. If I choose the custom object as the data record type, I can't get it to create an incident. 

    If I import using the second option above, the data is imported and I can view it in a report, but it does not create an incident and it does not show up in the incident view I created because there is no relationship from the custom object to an incident. I do have an incident id field in the custom object, but I can't map that to a non-existent incident on import.  I don't want to have to do an import to create a bunch of blank incidents and then do a second import of this data.

    How can I make the import for a custom object create an incident AND still be able to see those fields as individual fields on an incident?  This seems like a basic question but the help desk told me they could not answer it and I should post it here.
     

    Version:
    18A

    Best Comment

    Mary Gilbert

    If your custom object includes "Incident" and your fields are included there, you can use the data import wizard to do an incident import that will create new incidents and update those values.  Your import will have to include a value for c_id because all incidents must have an associated contact.

    Attached is a word doc with screenshots that show an example custom object that I created and I confirmed that I was able to successfully create an incident and update those fields in one step, using the data import wizard.

    I recommend that you test with a small number of rows in your import first, to make sure you are getting the desired results.

    Good luck!

    --Mary

    Comment

     

    • Edson Junior

      Try to explore the use of CPM. Here is some reference to read.

      Before move forward in this direction, make sure about the volume and frequency that it will happen. Sometime handle it outside such as through REST API / SOA would be a better alternative to your architecture.

      I hope this helps.

      Edson

    • Mary Gilbert

      If your custom object includes "Incident" and your fields are included there, you can use the data import wizard to do an incident import that will create new incidents and update those values.  Your import will have to include a value for c_id because all incidents must have an associated contact.

      Attached is a word doc with screenshots that show an example custom object that I created and I confirmed that I was able to successfully create an incident and update those fields in one step, using the data import wizard.

      I recommend that you test with a small number of rows in your import first, to make sure you are getting the desired results.

      Good luck!

      --Mary

      • Vivian Tedford

        Thanks for the info. What you are showing is the Incident area of a custom package.  I could add the fields there but there are so many and they are grouped together for a reason, I would prefer to keep them in their own custom object that is associated to the incident record.  But maybe it just can't be achieved that way.  I'll wait and see if anyone else offers suggestions.  I just didn't think this would be that strange of a use case.