Segment Code Bug Report

[LEE JONG GUN]

Hello

A "code" field was recently added to Segments. When using the Clone function, the code is also carried over (copied as-is) into the cloned segment, which prevents the clone from being saved.

Since the code value should be unique, the cloned segment ends up with a duplicate code and cannot be saved.

[JasonL]

Good catch! Thanks for bringing this to our attention. We’ll fix it so that cloning a segment doesn’t copy and inactivate the code field, avoiding the duplicate-code issue and allowing the clone to be saved.

[JasonL]

Hi @LEE-JONG-GUN,

Good news: the fix for the Segment code field clone bug has been deployed.

What changed

• When you clone a Segment now, the code field is automatically appended with _copy (e.g., myCode becomes myCode_copy).
• The cloned segment's code field is editable, so you can change it to any unique value and save the clone successfully.

This resolves the duplicate-code issue that was preventing clones from being saved. Thanks again for the report.

[LEE JONG GUN]

@JasonL Thanks for the update, and for getting this fixed.

One follow-up: now that _copy is auto-appended, the resulting code can
exceed the 12-character limit, and in that case the clone still can't be
saved. For example, a code that's already 8+ characters will go over the
limit once _copy is added.

Ideally, the code field should be editable during the clone step itself,
so the user can set a valid, unique code up front rather than relying on
an auto-generated suffix that may already break the length limit.

[JasonL]

All fields are editable during the cloning step, and the Code field is also editable there. I’m not sure why it’s looking like the Code field isn’t editable for you, it should work the same whether it’s under or over the 12‑character limit.

[LEE JONG GUN]

@JasonL At the time I reported this, that field was locked too, so it couldn't be edited — but I've now confirmed that it's editable.