Skip to content

create business event service cannot express unlimited attributes, collides with the CloudEvent id attribute, leaves V2 subject and channel name unmanaged #1525

Open

Description

@MendixMau

Summary

create business event service cannot express unlimited attributes, collides with the CloudEvent id attribute, and leaves the V2 subject and the channel name to a manual patch. Related, closed: #476 (reserved message attribute names), PR #533 (duplicate channels crash in the catalog).

Repro

  1. An app with the Business Events module. create business event service M.Svc ... message Msg ( EventId: String, Data: String );
  2. A long payload needs an unlimited attribute; MDL only offers String(200).
  3. Publishing with PublishBusinessEvent_V2: a Subject written via MDL needs a refresh (CE0115).
  4. Create the same service in a second app: the ChannelName differs per service.

Expected

A buildable publisher and subscriber from MDL alone: an unlimited length, a check diagnostic for the reserved CloudEvent member name, the V2 subject written consistently, and a way to state the ChannelName.

Actual

String(200) only; EventId duplicates an inherited CloudEvent member (reported by mxbuild); the V2 subject needs repair; the channel name is random, so two apps land on different topics.

Tested with: Mendix 11.15.0, mxcli v0.26.0 on macOS (code also read in the v0.27.0 source). Not retested on v0.27.0.

Activity

  1. github-actions commented on Oct 16, 2026

    @github-actions

    Issue Triage

    Summary:
    The create business event service command cannot define unlimited‑length attributes, clashes with the CloudEvent id field, and leaves the V2 subject and channel name to manual fixes.

    Checklist (bug report)

    Required info Present? Details
    mxcli version ✅ mxcli v0.26.0
    Mendix version ✅ Mendix 11.15.0
    Scenario (what was tried) ✅ Steps to create a business event service, need unlimited attribute, publish with PublishBusinessEvent_V2, etc.
    Expected output ✅ Buildable publisher/subscriber from MDL alone, unlimited length, diagnostic for reserved CloudEvent name, consistent V2 subject, explicit ChannelName.
    Experienced output ✅ Only String(200), EventId collides with CloudEvent id, V2 subject needs repair, channel name random across apps.
    AI bug report (mxcli diag --bundle or session log) ❌ Not provided.

    Missing information:
    Could you please attach the output of mxcli diag --bundle (or at least the relevant session log) so we can reproduce the environment and any internal diagnostics? Thanks!


    Automated triage via OpenRouter — workflow source

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions