Duplicate and Move Elements

What you'll learn:

• How to duplicate elements within the same page or to different pages
• How to move elements between different pages
• Understanding movement restrictions and limitations
• Managing element relationships and dependencies

Overview

The duplicate and move functionality allows you to reorganize your app's structure without rebuilding elements from scratch. When you duplicate or move an element, all its settings, filters, and configurations are preserved when possible, saving you time and ensuring consistency across your app.

📝All pending changes must be saved or discarded before duplicating or moving any elements.

Duplicating Elements

Within the Same Page

When you duplicate an element on the same page:

1. Select the element you want to duplicate
2. Choose Duplicate from the element menu
3. The new element appears directly below the original element
4. Modify the duplicate's settings as needed

Benefits of duplicating:

• Maintains all original settings and filters
• Creates a starting point for similar functionality
• Preserves connected relationships and permissions

To Different Pages

You can duplicate elements to other compatible pages in your app:

1. Select the element to duplicate
2. Choose Duplicate to Another Page
3. Select the target page from the dropdown menu
4. Confirm the duplication

Moving Elements

Between Pages

Moving elements transfers them completely from one page to another:

1. Select the element you want to move
2. Choose Move to Another Page
3. Select the destination page
4. Confirm the move

The element and all its settings transfer to the new location, removing it from the original page.

With Child Elements

When you move or duplicate an element that has child pages or elements, the entire structure moves together:

• Table elements include their details and edit pages
• Form elements maintain their field configurations
• Connected elements preserve their relationships

Movement Restrictions

Protected Elements

Certain elements cannot be moved or duplicated:

• Login pages - These must remain on their designated pages
• Registration pages - Cannot be relocated for security reasons

Page Hierarchy Rules

Elements cannot be moved into descendant pages that would create circular dependencies:

• A parent Table element cannot move to its own Edit page
• Elements cannot move to pages they helped create
• Child pages cannot become parents of their original parent elements

Table Source Requirements

Elements tied to specific tables have movement limitations:

• Edit forms can only move to pages using the same source table
• Details elements must share the same table source with the target page
• Connected elements require compatible table relationships

Permission Warnings

Private to Public Page Movement

When moving elements from private to public pages, you'll see warnings about:

• Potential security implications
• Changed access levels
• User visibility modifications

Role-Based Access Changes

Moving elements between pages with different user role access may ask for confirmation

• The element uses current logged-in user data as part of its source

Best Practices

Before Moving or Duplicating

• Save or discard all pending changes
• Review element dependencies and connections
• Check target page compatibility
• Consider user access implications

Organization Strategy

• Group related elements on appropriate pages
• Maintain logical page hierarchies
• Use duplication for similar functionality across different contexts
• Plan your page structure before extensive moving

Testing After Changes

• Verify element functionality in new locations
• Test user access and permissions
• Confirm data connections work correctly
• Review child element behavior

Troubleshooting

Common Issues

Element won't move to target page:

• Check if pages share compatible table sources
• Verify you're not creating circular dependencies
• Ensure target page isn't a descendant of the element

Missing options in target page dropdown:

• Only compatible pages appear in the selection
• Pages with incompatible table sources are filtered out
• The current page never appears as a move target

Permission warnings appearing:

• Review user role access between source and target pages
• Consider the security implications of the move
• Adjust page permissions if needed

💡 When in doubt about moving elements with complex dependencies, consider duplicating first to test functionality before committing to a permanent move.