Custom fields duplicate key row issue on upgraded db

[indikad]

we are test upgrading a client db from 6.5.13 to jiwa 7 - patch 117 and have a small issue getting existing custom fields to work ( a drop down list to start with )

There are 4 existing custom fields on 6.5.13
1 combo
3 text fields
they all have data on the db)customsettingValues too.

Tried the below and get an error.
Mys Steps:
Created our own custom field plugin - by creating the fields on Debtor master ( 4 or them ) - one being a combo box
added code to populate the combo box
the plugin work well on a blank demo database - tested fine.
imported the plugin to customer database that was upgraded from 6.5.13
get error below
"Cannot insert duplicate key row in object ....."
its refereeing to the field of type combo box. see attached error message.

Obviously the plugin is trying to create a custom field and finds it in the database but... How can I get this resolved please ?

I made sure the legacy plugins disabled - so its not interfering .

[Mike.Sheen]

Created our own custom field plugin - by creating the fields on Debtor master ( 4 or them ) - one being a combo box
added code to populate the combo box
the plugin work well on a blank demo database - tested fine.
imported the plugin to customer database that was upgraded from 6.5.13
get error below
"Cannot insert duplicate key row in object ....."
its refereeing to the field of type combo box. see attached error message.

Obviously the plugin is trying to create a custom field and finds it in the database but... How can I get this resolved please ?

I made sure the legacy plugins disabled - so its not interfering .

You probably will want to keep the existing values of the custom fields - so you should remove the custom fields in your new plugin which are already in the legacy plugin, then use the move button on the custom fields from the legacy plugin to move that field to your new plugin.

Mike

[indikad]

I will give this a try and post back. the bits I am worried about is the code that I have written for the new plugin.
In any case will give a try to your suggestion first.