User Tools

Site Tools


resolution_area:prometheus_resolutions:res-p9114

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
resolution_area:prometheus_resolutions:res-p9114 [2023/09/04 17:11] 10.91.120.100resolution_area:prometheus_resolutions:res-p9114 [2023/09/04 17:13] (current) 10.91.120.100
Line 102: Line 102:
 </code> </code>
  
-If the ticketer-integrations logs are showing that the ticket already exists in salesforce, (i.e. you are getting ""error":"duplicate value found: Originating_System_ID__c duplicates value on record with id"then its safe to just add entries into the ticketer.external_source table yourself. Just put in the salesforce case number, saleforce case ID and ticketer ticket id where appropriate (duplicate the three rows necessary and populate the info) +If the ticketer-integration logs are showing that the ticket already exists in salesforce, (i.e. you are getting ""error":"duplicate value found: Originating_System_ID__c duplicates value on record with id"and the RabbitMQ re-queue is not working. Then its safe to just add entries into the ticketer.external_source table yourself. Just put in the salesforce case number, saleforce case ID and ticketer ticket id where appropriate (duplicate the three rows necessary and populate the info). This is only a good idea when the ticket already exists in ATCs salesforce.
  
 **Auto Clear:** Yes, Alert will clear when the count of ATC DAS ticket was not created in Salesforce is 0 **Auto Clear:** Yes, Alert will clear when the count of ATC DAS ticket was not created in Salesforce is 0
resolution_area/prometheus_resolutions/res-p9114.1693843888.txt.gz · Last modified: 2023/09/04 17:11 by 10.91.120.100