Problem Summary
I'm attempting to migrate a WaveMaker project from version 9.4 to 10.6.6 and encountering persistent compilation errors related to type mismatches between Integer and BigInteger in the auto-generated Java service files. The errors occur specifically in foreign key relationship mappings across multiple database entities.
Environment
Source Version: WaveMaker 9.4
Target Version: WaveMaker 10.6.6
Database: SQL-based (specific RDBMS not mentioned, but appears to use auto-increment integer primary keys)
Error Details
The build fails with these type mismatch errors in the generated Java code. Here's the complete error log:
1. ERROR in /default/projects/CIPA_TEMP/master/services/WavemakerDB/src/com/cipa/wavemakerdb/CommAppInfo.java (at line 1403)
this.progId = commPrograms.getProgId();
^^^^^^^^^^^^^^^^^^^^^^^^
Type mismatch: cannot convert from Integer to BigInteger
2. ERROR in /default/projects/CIPA_TEMP/master/services/WavemakerDB/src/com/cipa/wavemakerdb/CommEquInfo.java (at line 234)
this.appId = commAppInfo.getAppId();
^^^^^^^^^^^^^^^^^^^^^^
Type mismatch: cannot convert from Integer to BigInteger
3. ERROR in /default/projects/CIPA_TEMP/master/services/WavemakerDB/src/com/cipa/wavemakerdb/CommResponse.java (at line 162)
this.bldgId = commBldgInfo.getBldgId();
^^^^^^^^^^^^^^^^^^^^^^^^
Type mismatch: cannot convert from Integer to BigInteger
4. ERROR in /default/projects/CIPA_TEMP/master/services/WavemakerDB/src/com/cipa/wavemakerdb/CommResponse.java (at line 192)
this.equId = commEquInfo.getEquId();
^^^^^^^^^^^^^^^^^^^^^^
Type mismatch: cannot convert from Integer to BigInteger
5. ERROR in /default/projects/CIPA_TEMP/master/services/WavemakerDB/src/com/cipa/wavemakerdb/CommResponse.java (at line 207)
this.locId = commLocInfo.getLocId();
^^^^^^^^^^^^^^^^^^^^^^
Type mismatch: cannot convert from Integer to BigInteger
6. ERROR in /default/projects/CIPA_TEMP/master/services/WavemakerDB/src/com/cipa/wavemakerdb/Uwcomments.java (at line 129)
this.uid = users.getUid();
^^^^^^^^^^^^^^
Type mismatch: cannot convert from BigInteger to Integer
Affected Entities and Relationships
The errors span multiple entity relationships:
CommAppInfo←CommPrograms(progId foreign key)CommEquInfo←CommAppInfo(appId foreign key)CommResponse←CommBldgInfo(bldgId foreign key)CommResponse←CommEquInfo(equId foreign key)CommResponse←CommLocInfo(locId foreign key)Uwcomments←Users(uid foreign key)
What We've Tried
Manual code fixes: Attempted to manually modify the generated Java files, but WaveMaker refuses to compile, enforcing that all database changes must occur through the UI.
Database re-import through UI: Attempted to re-import the database through WaveMaker's database import wizard, but the type mismatches persist.
Reviewed WaveMaker training materials: Completed all WaveMaker courses to ensure proper usage of the platform's database management features.
Contacted WaveMaker support: Received no actionable solution from official support.
Version 9.4 re-import: Attempted to re-import the database in version 9.4 before migration, which produces the same errors shown above.
Root Cause Hypothesis
We believe the database schema was modified outside of WaveMaker's UI at some point (possibly direct SQL alterations), causing WaveMaker's internal schema representation to fall out of sync with the actual database structure. The migration from 9.4 to 10.6.6 may have also changed how WaveMaker maps certain SQL integer types to Java types, exacerbating the inconsistency.
The foreign key columns appear to have inconsistent type mappings - some tables have fields defined as Integer while their related tables return BigInteger for the same logical ID column.
Questions
Is there a way to force WaveMaker to regenerate all entity mappings from scratch based on the current database schema, rather than relying on cached metadata from the 9.4 project?
How can we resolve type inconsistencies in foreign key relationships when WaveMaker's code generator produces mismatched types across related entities?
Is there a configuration or mapping file we can manually edit to specify Java type mappings for specific database columns before code generation?
Has anyone successfully migrated a WaveMaker 9.x project to 10.x with similar Integer/BigInteger type conflicts? What approach worked?
Are there known changes in how WaveMaker 10.6.6 maps SQL integer types (INT, BIGINT, etc.) to Java types compared to 9.4?
Additional Context
Foreign keys are correctly defined in the database schema (verified via direct database inspection)
The same errors occur whether we migrate directly or re-import in 9.4 first
We cannot roll back WaveMaker versions for testing purposes
The project built successfully in WaveMaker 9.4 before migration
Any guidance on resolving these type mapping inconsistencies would be greatly appreciated. We're blocked on this migration and need to get the project running on 10.6.6. Thank you all for your contributions. I am grateful for this community!