ALIM Web "invalid column name 'co_id'" error when creating Documents

When trying to create a document from template in ALIM Web, I get the following error: invalid column name 'co_id' This only happens to a few classes of documents, and it only happens in ALIM Web.  For example, my class path for LOAs is 'Procedures>LOAs', and I know that anything that is a subset of the Procedures class will give me the above error.  However, my class path for Work Instructions is 'Work Control Docs>Work Instructions', and everything under the Work Control Docs parent class works fine.  If I move my LOAs class so that it is a child of 'Work Control Docs', the error will go away.  The new path of 'Work Control Docs/LOAs' works just fine.  I have compared the 'Procedures' and 'Work Control Docs' classes in every way imaginable.  They look the same in the database, they have the exact same setting, etc.  Since this problem only persists in ALIM Web, I am led to believe it is a web setting, but I wouldn't know where to begin.  

Parents
  • This is likely not due to a web setting or layout. It is probably happening on documents that are subject to change packages (i.e. classes that use prototypes/markups). There is an incompatibility between some api calls and the prototypes table that occurred at ver 16.8. At this point, the "co_id" column was removed from the prototypes table (you can check this in your database), but some of the procedures still referred to it. First, make sure that the nuclear module is the correct version for your core version. Then run the database upgrade scripts for both the core and nuclear packages in the SMC. If this does not align the the procedures and the tables, you will need to file a service request. It would be a lot of work for just this, but upgrading to the current version 16.9 would fix it. 

    Eric Rajala | Consultant

    Cohesive

    Email: eric.rajala@cohesivegroup.com

    www.bentley.com

       
    This is a test

Reply
  • This is likely not due to a web setting or layout. It is probably happening on documents that are subject to change packages (i.e. classes that use prototypes/markups). There is an incompatibility between some api calls and the prototypes table that occurred at ver 16.8. At this point, the "co_id" column was removed from the prototypes table (you can check this in your database), but some of the procedures still referred to it. First, make sure that the nuclear module is the correct version for your core version. Then run the database upgrade scripts for both the core and nuclear packages in the SMC. If this does not align the the procedures and the tables, you will need to file a service request. It would be a lot of work for just this, but upgrading to the current version 16.9 would fix it. 

    Eric Rajala | Consultant

    Cohesive

    Email: eric.rajala@cohesivegroup.com

    www.bentley.com

       
    This is a test

Children
No Data