Is it possible that if the custom fields added to HPD:IncidentInterface from the second form join HPD:Help and not from the first HPD:Help (the HPD:IncidentInterface is a join form between HPD:Help and HPD:Help), causes that effect?
You need to enable the logs and check why 2 records are created. Traces with user id AR_AUDITOR are need to check for this.
And one more thing is that whether these 2 records are created for same Create Operation (which should not be the case) or (Create and Set Operation) which will be tracked in Action field.
We had duplicate entries when we were using auditing on the AST:Attribute form, and have a current case opened with BMC for it. This case has been opened for about a year and exists in v9.1.01 and 9.1.03. It seems to have something to do with having Sandbox enabled, at least from our end, because when we disable sandbox there is no duplication of record. Since we use sandbox, that option can not be a solution for us.
On very high level, if the qualification criteria in auditing is set to "DatasetID = BMC.Asset" then that should overcome.
It was not that simple. Most of our records in the AST:Attribute form do not have any value in the DatasetId field.
This is where I ended up last, maybe it can help you.
I have audit turned on for Installation Date, Disposal Date, and AssetLifecycleStatus fields. After changing one of these fields and opening Lifecycle Audit quick link, the update is displayed twice (identical time) with same values. The log I had running shows the active link that updates the table running twice (AST:SLG:SystemAuditTableChoice)