HTML Architect: MappedObjectName field population

ideas
,
1

The MappedObjectName field, for example for a DB entity or DB field, should be automatically populated based on the Name field — currently, the user has to re-enter it manually

3
4

Hi everyone,

I just pushed a small UX improvement to the HTML Architect grid editor that I thought was worth sharing.

Until now, whenever you were editing a schema item that has a MappedObjectName field (e.g. a DB entity or a DB field), you had to retype the same value into MappedObjectName after filling in Name. A bit annoying, especially when creating lots of new items where the two values are almost always identical.

So I made the grid editor auto-fill MappedObjectName from Name as you type.

How it works:

  • When you edit the Name property in the grid editor, it checks whether the same item also has a MappedObjectName property.
  • If MappedObjectName is empty or still equals the previous Name value (meaning you’ve never customized it), the new Name value gets copied into MappedObjectName reactively — you can see it updating in the UI on every keystroke.
  • If you’ve already typed a custom value into MappedObjectName that differs from Name, it’s left untouched — the auto-fill never overwrites manual input.
  • The synced value is sent to the backend together with the Name change, so it persists normally.

The behavior mirrors the existing OnNameChanged logic in TableMappingItem on the backend, but I moved this convenience into the frontend so you see the field update live while editing instead of only after a round-trip (blocked by FE restrictions).

Let me know if you run into any edge cases!

5

I also extended the auto-fill to MappedColumnName for new database fields, refactored both cases into a shared loop, and re-tested.

6

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.