'Incident Number' and 'Instance Id' should be Unique for each Incident Request in the HPD:HelpDesk Form.
If you are still facing the same issue, then I will suggest you to please take the Filter logs of your activities,
and see wrt which filter you are getting this issue.
If you have any difficulty in understanding then paste the logs here.
I was getting same issue while using the Ctrl + T option as the entry was creating the unique index.
This error may also occur if the entry is saved on the database and again if you are trying the same entry.
Try by running the below query on database or check by restarting AR service if it could help to resolve this issue.
update arschema set nextId = 5850 where name = 'HPD:Help Desk'
HPD:Help Desk form contains some fields which does not allow duplicate values.
Incident Number(1000000161) and Instance ID(179) are two of those fields having Unique indexing active.
If you want more information then reply me...
What I understood (may be) If you are creating new entry by using Ctrl+T, after every entry the AR System create unique instace for it and its unique for every entry. ARS attempt to create new entry with older Instace id.
So, use F2 for every entry.
Thanks & Regards
For me, it was an expired license key when I received the ARERR 382 error when I was trying to save a Known Error.
Thanks for your suggestions.
I was trying to do 'Copy To New' and when I was trying to save a record getting that error message.
I opened a Ticket with BMC, once I get reply then I let you know .
Thanks & Regards
"Copy to New" will do exactly as it says on the label, copy the current values to a new record including Instance Id's and hidden fields.
Therefore this is a default system message and not a bug. Support should tell you this as well.
If you want to use this functionality, then you need to clear out the fields that are system generated or the error will continue to occur when using this functionality ......
Did you get any replay from BMC...I ma getting same error:
The value(s) for this entry violate a unique index that has been defined for this form : schema: HPD:Help Desk, entry: INC000000000638, 2 unique index(es), field(s): 1000000161 179 (ARERR 382)
Did you try what Carl explained earlier ???
I did not use Copy functionality. It was fresh incident creation.
We are using ITSM 8.1.
Next Block ID is set to 100.
that is not possible, the field 179 is a unqiue GUID which is generated on creation - the only way that this can violate a unique index is if it was somehow copied from one request to another.