Not sure about custom transactions, but we have seen this with regular transactions. we have 2 bundles that tried to add fields with the same name (But different ids) and got that error. the solution was to relabel one of the field with " 2" at the end of it on our custom form