Skip to content

Some model writes drop Studio Pro's OneTimeConversions entry, so Studio Pro asks to convert again #1917

Open

Description

@marco-van-malsen

Versions: mxcli v0.32.0, mendix 11.16.1, toolkit v2026.11.17-6-g1a56c3a1

Steps to reproduce

Open an MPR v2 project (Mendix 11.16.1) in Studio Pro 11.16.1; it records UseMeToSetupNodeConversion in the ProjectConversion unit (OneTimeConversions 119 -> 120). Later mxcli writes return the unit to 119 items: seen after mxcli marketplace update (v0.32.0, with fix widgets/design-properties, 0 units altered by those) and after earlier exec rounds. Reopen in Studio Pro.

Expected

mxcli preserves the ProjectConversion unit (or entries it does not know); Studio Pro opens without a conversion prompt.

Actual

Studio Pro reports the project was last saved with 11.16.1 and offers Convert in-place; accepting re-adds the entry and re-saves every mxcli-written unit with identical properties (161, 184, 191 units on three occasions).

Workaround

Accept the in-place conversion and commit it on its own; diff-local shows identical properties.

Activity

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