Business event MESSAGE attribute names reject common identifiers as reserved keywords

[retran]

Summary

When creating a business event service, MESSAGE attribute names that happen to be MDL reserved keywords are rejected by the parser, even though they are valid domain concepts.

Reproduction

CREATE BUSINESS EVENT SERVICE MyModule.Events
(ServiceName: 'Svc', EventNamePrefix: 'com.test')
{
  MESSAGE OrderCreated (Date: DateTime, Amount: Decimal) PUBLISH ENTITY MyModule.Order;
};

Error: Parse error: mismatched input 'Date' expecting IDENTIFIER

Affected keywords (tested)

Date, Created, Amount, Timestamp — all common attribute names rejected as reserved.

Expected behavior

The parser should allow identifierOrKeyword (not just IDENTIFIER) in MESSAGE attribute name position, or business event attribute names should use a separate lexer mode.

Workaround

Use non-keyword names: EventDate, TotalAmount, CreatedAt.

Version

mxcli v0.7.0-368-g5a109a0e

[github-actions]

Issue Triage

Summary:
The parser incorrectly treats MDL reserved keywords (e.g., Date, Amount) as invalid identifiers in MESSAGE attribute names when defining a business event service.

Checklist for bug report completeness

Required info	Present?	Details
mxcli version	✅	mxcli v0.7.0-368-g5a109a0e
Mendix version	❌	Not specified
Scenario (what the user was trying to do)	✅	MDL script creating a business event service
Expected output	✅	Parser should accept identifierOrKeyword (e.g., Date) as attribute names
Experienced output	❓	Error message shown (Parse error: mismatched input 'Date' expecting IDENTIFIER) – present, but no session log/diag bundle
AI bug report (mxcli diag --bundle or session log)	❌	Not provided

Missing information:

• The Mendix version of the project being processed.
• A diagnostic bundle or session log from mxcli diag --bundle (or at least the relevant log output) to help reproduce the issue.

Could you please add the Mendix version and, if possible, attach the output of mxcli diag --bundle (or the relevant session log)? Thank you for reporting this!

---

Automated triage via OpenRouter — workflow source