Process Mapping Logo

Process Mapping - Forums

Sharing 19 years of knowledge and experience

Metastorm BPM forums
Sign up Latest Topics

  Author   Comment  

Avatar / Picture

Posts: 5,507
Reply with quote  #1 

Changing the Datatype of an e-Work Variable

Last edited: 28 Feb 2005

The information in this article applies to product: e-Work all versions


  • When a procedure is published, the following message appears:

    Warning - Column <columnname> is already defined with a different field type


  • This message indicates that a column has already been created in the map table in the e-Work database for the e-Work variable but with a different datatype. The following steps would generate this warning:
    1. Add a number field to a form and associate it with custom variable 'Number1' of type 'integer'.
    2. Publish this as 'Map1'. In the table 'Map1', a column will be created named 'Number1' of type 'int' (in SQL Server).
    3. In the e-Work Designer, delete the custom variable 'Number1'. Now create a new custom variable with the same name but of datatype 'real'.
    4. Publish the procedure. The warning listed above will be generated. Column 'Number1' already exists in the database as type 'int', and e-Work cannot change the datatype of a pre-existing database column. Either create an e-Work variable with a different name to associate with the form field, or change the datatype in the database.

Keywords: kb499

Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.
Previous Topic | Next Topic

Quick Navigation:

Create your own forum with Website Toolbox!