Skip to content

Fix: trigger GenericObject dropdown fields migration - #1239

Merged
Rom1-B merged 1 commit into
mainfrom
support_43878
Aug 6, 2026
Merged

Fix: trigger GenericObject dropdown fields migration#1239
Rom1-B merged 1 commit into
mainfrom
support_43878

Conversation

@Rom1-B

@Rom1-B Rom1-B commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Checklist before requesting a review

Please delete options that are not relevant.

  • I have performed a self-review of my code.
  • I have added tests (when available) that prove my fix is effective or that my feature works.
  • I have updated the CHANGELOG with a short functional description of the fix or new feature.
  • This change requires a documentation update.

Description

  • It fixes !43878
  • The migration guard that detects legacy GenericObject dropdown fields read the wrong result key from the count query, so it always evaluated to false.
  • As a result, GenericObject dropdown fields were never migrated to CustomAsset dropdown fields, and affected fields displayed the wrong label on item forms.

Screenshots (if appropriate):

@Rom1-B
Rom1-B requested a review from MyvTsv August 6, 2026 11:12
@MyvTsv

MyvTsv commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

That looks good to me. I'll wait for the client's feedback before approving the fix.

@Rom1-B
Rom1-B merged commit 95426b2 into main Aug 6, 2026
3 checks passed
@Rom1-B
Rom1-B deleted the support_43878 branch August 6, 2026 13:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants