gemini/gemini-3.1-pro-preview
Known Shortcomings (16)
Sorted by occurrence count (most frequent first)
| # | Concept | AL Concept | Count | Affected Tasks |
|---|---|---|---|---|
| 1 | empty-or-missing-code-generation | interface-definition | 2 | CG-AL-H021, CG-AL-M009 |
|
Description: The model failed to generate any valid AL code at all. The compilation error AL0198 'Expected one of the application object keywords' at position 1:1 indicates the generated file was either empty or contained no recognizable AL object declarations. The task required creating an interface 'INotificationChannel', three implementing codeunits (70221, 70222, 70223), and a manager codeunit (70220) using List of [Interface] and Dictionary of [Text, Interface] collections. The model produced no code (noted as 'Generated code not found'), resulting in a completely empty or invalid file.
Correct Pattern:
Incorrect Pattern:
Error Codes: AL0198, AL0104 |
||||
| 2 | empty-or-missing-code-generation | table-definition | 2 | CG-AL-M003, CG-AL-M112 |
|
Description: The model failed to generate any valid AL code at all. The compilation error AL0198 'Expected one of the application object keywords' at position 1:1 indicates the generated file was either empty or contained no recognizable AL object definition. The task required creating a complete 'Sales Contract' table (ID 70002) with fields, triggers, and validation logic, but the model produced no output (or invalid non-AL content). The task definition and test file are both correct and well-specified.
Correct Pattern:
Incorrect Pattern:
Error Codes: AL0198 |
||||
| 3 | empty-or-missing-code-generation | codeunit-definition | 1 | CG-AL-E050 |
|
Description: The model failed to generate any valid AL code at all. The compilation error AL0198 'Expected one of the application object keywords' at position 1:1 indicates the generated file was either empty or contained no recognizable AL object declaration. The model should have produced a codeunit with ID 70050 named 'CG Text Builder' containing three procedures (GetSqlQuery, GetJsonTemplate, GetEmailBody) using multiline string literals. The task and tests are perfectly valid - the model simply failed to produce any output.
Correct Pattern:
Incorrect Pattern:
Error Codes: AL0198 |
||||
| 4 | table-extension-with-page-extension | page-extension | 1 | CG-AL-E006 |
|
Description: The model failed to generate any code at all ('Generated code not found'). The task requires creating both a table extension on the Customer table (table 18) to add the new fields ('Preferred Contact Method', 'Customer Notes', 'VIP Customer') and a page extension on the Customer Card (page 21) to display those fields in the General group. The compilation errors show that the Customer record doesn't contain the new fields, meaning the model did not produce the necessary table extension to define these fields, nor the page extension. The model either produced empty output or output that wasn't captured.
Correct Pattern:
Incorrect Pattern:
Error Codes: AL0132 |
||||
| 5 | al-syntax-structure | codeunit-procedure-syntax | 1 | CG-AL-H022 |
|
Description: The model generated code with syntax errors around line 107 of the output file. The compilation errors (Expression expected, ')' expected, 'end' expected) indicate the model produced malformed AL code, likely with incorrect procedure signatures, missing begin/end blocks, or improper use of RecordRef/FieldRef APIs. The generated code was not captured ('Generated code not found'), but the errors at line 107 suggest the model struggled with the complex procedure definitions involving var parameters, Variant types, or error handling patterns (TryFunction or if/then with RecordRef.Open). The task and test definitions are valid - this is a model failure to produce syntactically correct AL code for advanced RecordRef/FieldRef manipulation patterns.
Correct Pattern:
Incorrect Pattern:
Error Codes: AL0224 |
||||
| 6 | secrettext-isolated-storage-syntax | secrettext-handling | 1 | CG-AL-H016 |
|
Description: The model failed to generate valid AL code for the 'CG Secure Storage' codeunit. The compilation errors (AL0104 syntax errors around line 21) indicate the model produced syntactically invalid AL code, likely struggling with SecretText type handling, IsolatedStorage API usage with SecretText parameters, and the correct syntax for unwrapping SecretText values. The generated code was not even captured ('Generated code not found'), suggesting the model either produced malformed output or failed to properly structure the codeunit. The task and tests are valid - the model simply lacks sufficient knowledge of SecretText patterns in AL, including how to use IsolatedStorage.Set/Get with SecretText, how to unwrap SecretText values, and how to properly work with the SecretText type in procedure signatures.
Correct Pattern:
Incorrect Pattern:
Error Codes: AL0104 |
||||
| 7 | empty-or-missing-code-generation | al-object-definition | 1 | CG-AL-H005 |
|
Description: The model failed to generate any valid AL code. The compilation error AL0198 'Expected one of the application object keywords' at position 1:1 indicates the generated file was either empty or contained no recognizable AL object definitions. The task required creating two tables (CG Audit Log 70206 and CG Tracked Item 70207) with specific fields and an OnModify trigger, but the model produced no code at all (or invalid non-AL content).
Correct Pattern:
Incorrect Pattern:
Error Codes: AL0198 |
||||
| 8 | table-field-naming-conventions | api-page-with-backing-table | 1 | CG-AL-M001 |
|
Description: The model failed to generate any code at all ('Generated code not found'). The task required creating both a Product table and a 'Product API' page. The compilation errors show that the test file references Product."No." which means the model needed to create a Product table with a field named "No." (Code[20]) as the primary key, along with Description, "Unit Price", "Stock Quantity", "Category Id" fields, and an API page exposing these with camelCase field names (productCode mapping to "No.", description, unitPrice, stockQuantity, categoryId). The model produced no output whatsoever, indicating a fundamental failure to generate the required AL objects (table + API page) for this medium-complexity task.
Correct Pattern:
Incorrect Pattern:
Error Codes: AL0000 |
||||
| 9 | errorinfo-customdimensions-codeunit-structure | error-handling-errorinfo | 1 | CG-AL-H007 |
|
Description: The model failed to generate valid AL code for the codeunit and enum. The compilation errors at line 29 (syntax error, ':' expected, 'begin' is a keyword) indicate the model produced structurally malformed AL code - likely missing or malformed procedure signatures, or incorrectly structured the codeunit/enum definitions. The generated code was not even captured ('Generated code not found'), suggesting the model may have produced output that couldn't be properly parsed, or produced code with fundamental structural issues like missing procedure declarations before 'begin' blocks. The task and tests are valid; the model simply failed to produce correct AL syntax for ErrorInfo.Create(), CustomDimensions dictionary usage, and proper codeunit structure.
Correct Pattern:
Incorrect Pattern:
Error Codes: AL0104 |
||||
| 10 | al-conditional-syntax | control-flow-syntax | 1 | CG-AL-M005 |
|
Description: The model generated AL code with syntax errors around conditional statements (if/then/else blocks) at line 104 and surrounding lines. The compilation errors indicate missing 'then' keyword and mismatched 'end' statements, which are fundamental AL syntax issues. The generated code was not captured/saved but the errors clearly show the model produced malformed control flow structures in the codeunit implementation. This is a model knowledge gap in producing syntactically correct AL conditional logic, likely involving retry logic or error handling patterns requested by the task.
Correct Pattern:
Incorrect Pattern:
Error Codes: AL0104 |
||||
| 11 | complex-codeunit-generation-syntax | codeunit-with-interface-and-recordref | 1 | CG-AL-H023 |
|
Description: The model failed to generate syntactically valid AL code for a complex codeunit involving RecordRef/FieldRef manipulation, interfaces, and multiple procedures. The compilation errors at line 25 (semicolon expected, 'end' expected) and line 35-36 (expression expected, multiple semicolon errors) indicate the model produced malformed AL code with fundamental syntax issues - likely incorrect procedure declarations, missing begin/end blocks, or improperly structured interface definitions. The generated code file was noted as 'not found' in the analysis but the compilation errors clearly show the model attempted to generate code that had basic structural/syntax problems. This is a complex task requiring 10 procedures, an interface definition, and extensive use of RecordRef/FieldRef APIs, which the model failed to produce correctly.
Correct Pattern:
Incorrect Pattern:
Error Codes: AL0111 |
||||
| 12 | al-conditional-syntax | control-flow-statements | 1 | CG-AL-M008 |
|
Description: The model generated AL code with syntax errors in conditional statements (if/then/else blocks). The compilation errors indicate issues at line 22 with 'then' expected, orphaned ELSE statements due to unnecessary semicolons before ELSE keywords, and general structural syntax problems. The generated code was not captured but the errors clearly show the model produced malformed if-then-else constructs and had semicolons before ELSE keywords, which is a common AL syntax mistake. The task and test definitions are valid - this is purely a code generation quality issue.
Correct Pattern:
Incorrect Pattern:
Error Codes: AL0104 |
||||
| 13 | multi-object-al-file-structure | al-object-definition-syntax | 1 | CG-AL-M010 |
|
Description: The model generated syntactically invalid AL code for a multi-object scenario. The compilation errors (AL0124 'The property Data cannot be used in this context', AL0104 syntax errors for '=' expected, '{' expected, '}' expected, and AL0198 expecting application object keywords) indicate the model produced malformed AL object definitions. The errors suggest the model likely used incorrect property syntax (e.g., a 'Data' property that doesn't exist in the context used), had structural issues with object definitions (missing or misplaced braces/equals signs), and failed to properly separate or define multiple AL objects (table, page, codeunit) in a single file. The task and tests are valid - this is purely a model code generation failure.
Correct Pattern:
Incorrect Pattern:
Error Codes: AL0124 |
||||
| 14 | yaml-parsing-al-syntax | string-parsing-control-flow | 1 | CG-AL-M021 |
|
Description: The model generated AL code with syntax errors around line 20 and 143, likely involving incorrect control flow syntax (missing 'then' after 'if' conditions, incorrect block structure). The compilation errors indicate the model produced malformed AL code with syntax issues in conditional statements and block endings. The task and tests are valid - the model simply failed to produce syntactically correct AL code for YAML string parsing logic. The errors at lines 20 and 143 both show 'then expected' followed by 'end expected', suggesting the model used an incorrect pattern for if-then blocks, possibly mixing syntax from another language (e.g., using curly braces or missing 'then' keyword after if conditions).
Correct Pattern:
Incorrect Pattern:
Error Codes: AL0104 |
||||
| 15 | complex-report-with-helper-codeunit | report-definition-and-codeunit-generation | 1 | CG-AL-M007 |
|
Description: The model failed to generate any valid AL code at all. The task required creating both a Report 70001 'Sales Performance Analysis' and a helper codeunit 'CG-AL-M007 Mock Calculator' that the test file references. The compilation error AL0198 indicates the generated file was empty or contained no valid AL object declaration. The model needed to produce: (1) a report object with Customer, Sales Header, and Sales Line data items with complex calculations, and (2) a codeunit implementing MockCalculator with procedures like Initialize, AddSalesLine, GetRunningTotalByCustomer, GetRunningTotalByRegion, CalculateAverageOrderValue, GetCustomerRank, GetTopProduct, GetProductSalesQuantity, CalculateYoYComparison, CalculateOrderFrequency, GetTotalSales, and GetCustomerCount. The model produced no code (empty output).
Correct Pattern:
Incorrect Pattern:
Error Codes: AL0198 |
||||
| 16 | string-literal-termination | al-syntax-basics | 1 | CG-AL-M004 |
|
Description: The model generated AL code with improperly terminated text literals (string constants). The compilation errors AL0360 at line 103 and 105 indicate that single-quote delimited string literals were not properly closed. This is a basic AL syntax issue where the model likely included an unescaped single quote within a MESSAGE string or used incorrect quoting. For example, in the ApplyDiscount action's Confirm/Message call, the model probably wrote a string containing an apostrophe that broke the literal, or split a string across lines incorrectly.
Correct Pattern:
Incorrect Pattern:
Error Codes: AL0360 |
||||