Service Connect testing for existing records

Hi everyone,
I am working on a workflow to bring in Jira worklogs into Epicor 9. I am planning on pulling in the worklog records and putting them into a ud table and putting the worklogid in Key1. I am trying this with a Getanew method then performing the update for the additional data. I would have expected the workflow to fail if I attempted to put the same worklogid into a new record, but that does not appear to be the case, the workflow just works, which is not what I want.

Looking in SQL I see the index on company, key1,key2,key,key4 and key5. Just putting in the company key1 I would have thought would be enough to trigger the constraints on the table and throw an error, which I could then abort the workflow as I don’t want duplicates.

Any suggestions or a better way is appreciated.

Cheers
Simon

A bit of further information. I tested just doing a GetaNewUD08 and putting the values into the conversion prior to the method. I did not populate key5 and get the error [UD08], error [Column ‘Key5’ does not allow DBNull.Value.]
Looking at the SQL schema of the database it shows that it does accept nulls. Is this related to the progress schema?