If you create the field in the opportunity entity, then create the field in the opportunityprogress entity, with exactly the same column name.

You should then receive the above message, which reads: -

This column name already exists on another table. Therefore this field must have the same properties as the existing field. If you want to make a different field, it must have a unique column name

This will then allow the field to act like any other in the opportunityprogress table.

As Toby has said you have to create the fields via the Opportunity Progress in the Secondary Entities part of Commiseration, but I thought it best to mention that if you have CRM 7.1SP2 and do not have at least patch F (I Think it was this one that fixed the problem) then you will get the error "This column name is already used in existing views. Please enter a different column name "

So if the CRM version is Prior 7.1SP2 you will be OK or if you have the 7.1 SP2 version make sure you are on the latest patch.

I am attempting to add a field to the Opportunity Progress entity and am receiving "This column name is already used in existing views. Please enter a different column name."

We are currently using 7.1.f.s

Hi All,

Unfortunately we are using 7.1 and yes we get the error message when you create the field :(

We managed to get around this by creating the field in SQL Studio Manager, using the same field name and type.

This appears to be working and the field data is pulled through from the opportunity.

Many thanks

Adding the field in SQL studio manager worked perfectly.

Once adding the fielding, I had to perform a Metadata Refresh and tada!!! I now have access to the information.

Thanks for your assistance.