[Bug Report] Missing Block Configuration Options in V2 Map Block (vs V1)

English Forum
1

Environment:

  • NocoBase version: 2.0.0-beta.13
  • Installation method: create-nocobase-app
  • OS: Ubuntu Server 24.04.3
  • Block type: Map Block

Summary:

Several essential block configuration options available in V1 (Classic pages) are missing in V2 (Modern pages) Map Block settings.

Detailed Comparison:

:white_check_mark: V1 Block Settings (13 options): Link demo https://a_8hwne7u84ho.v13.demo.nocobase.com/admin/on02hifb4i3

image
image1280×482 68.4 KB

![V1 Map Block settings showing all available options]

Available options:

  1. Edit block title & description
  2. Set block height
  3. Block Linkage rules
  4. Map field → Location
  5. Marker field → Name
  6. Concatenation order field
  7. Set data loading mode :warning:
  8. The default zoom level of the map
  9. Set the data scope
  10. Connect data blocks :warning:
  11. Save as reference template
  12. Delete

:x: V2 Block Settings (10 options): Link demo: https://a_8hwne7u84ho.v13.demo.nocobase.com/admin/gxpzwd86ai1

image
image1280×496 69.7 KB

![V2 Map Block settings with missing options]

Available options:

  1. Title & description
  2. Block linkage rules
  3. Map Field & Marker field
  4. Data scope
  5. Concatenation order field
  6. The default zoom level of the map
  7. Edit popup
  8. Save as template
  9. Copy UID
  10. Delete

Missing Features in V2:

Feature Impact Use Case
Set data loading mode Cannot configure lazy loading vs eager loading Performance optimization for large datasets
Connect data blocks Cannot link this block to filter/sync with other blocks Interactive dashboards with multiple blocks
Set block height Must use custom CSS workarounds Responsive layout design

Questions:

  1. Are these features planned for V2?

    • If yes, what’s the expected timeline?
    • If no, what are the recommended workarounds?

  2. Is “Connect data blocks” replaced by another mechanism in V2?

    • In V1, this was crucial for building interactive dashboards.

  3. How to set block height in V2?

    • Should we use FlowEngine APIs or custom CSS?

Additional Context:

This is similar to my previous report about "Field component" missing in Form fields.

It seems like V2 is missing several configuration options that were standard in V1, which affects our ability to migrate existing applications.

Expected Behavior:

V2 block settings should have feature parity with V1, or provide alternative mechanisms to achieve the same functionality (e.g., via FlowEngine APIs).

Thank you for your attention! Looking forward to understanding the roadmap for these features. :pray:

2

Thank you for your feedback. Block height and loading mode features will be included in future plans.

The filter form is a new feature and does not require linked blocks.

Reference

1 Like