Ability to Copy/Move a Block to a Different Page

I’m grateful for the ability to duplicate a block and move it to another tab on the current page, but to take it one step further, I’d love the ability to copy an entire block and paste it on a completely different page.

image

13 Likes

Ooof, I’ve come across this too. THANK YOU, this would be super useful, especially for those more complex detail blocks where there’s a million conditions you have to rebuild :sweat_smile:

2 Likes

Similarly, the ability to save any custom blocks one creates as reusable template blocks would be super helpful. Most apps only deploy a few different page layouts so the ability to create page using elements of other, existing pages - or templates created and saved while building a different project - would be very helpful. In Figma, for example, one can save variants, custom design elements, etc and apply these resources to future designs.

8 Likes

@akraut my GOODNESS that would be one of the most used features for me by far.

2 Likes

Most definitely! I requested that one already too!!! Ability to save pre-configured page layout templates (Page Template Library?)

1 Like

While copy-pasting elements would be a great start, it would be even better if we could save elements as “global views” or “global elements.” This feature would allow us to:

  • Paste similar elements / views (+ settings) around the workspace easily.
  • Define whether a specific element/view needs to be connected to the global element.
  • Apply changes to the global element, which applies it to all connected elements in the workspace.

This approach would ensure consistency and integrity across similar views / designs on blank pages, making it easier to create and manage complex portals with multiple suites. It would streamline future updates and changes you make to these elements, maintaining a logical and coherent structure throughout the workspace

3 Likes

Ooof, thank you. Can’t tell you how many times I’ve needed to be able to copy and paste a block to a different page… takes up so much time rebuilding components.

1 Like

Bumping this up because I wanted to suggest the same thing :slight_smile:

2 Likes

Any news on this front?

This would save so much time and make building/maintaining apps so much enjoyable and efficient.

Example: I Spend half an Afternoon carefully crafting a Multitab Page with 10+ Action buttons and Filters for multiple Collections.
Now it became obvious that this page needs to be merged with another Page. I have zero chance to reuse any of the work I already did but rather I have to rebuild everything from scratch.

Back again to upvote this… probably my BIGGEST pain point currently. :confused:

1 Like

It would be VERY helpful

1 Like

+1 for this :smiley: “Save Component” may be a nice feature where you could have pre-setup components in a library to select from… similar to how ClickFunnels does it

Example: ClickFunnels Example Save Templates

1 Like

I’m going to set this as a new feature request - 100% agree - this is needed because it is quite annoying to have to go to all of the different pages to make the same update to a block that should be identical across pages!

2 Likes

Plus one from me as well.

3 Likes

@darragh Wondering what the status on this feature is?

We’ve been delaying some redesigns hoping copy & paste will be possible soon (its 50-100 hours without copy paste vs. 3-5 with it).

It also feels like this feature is quite essential, especially considering there are currently zero options for saving collections or Buttons as template.

Right now, so much time is wasted on building the same things (buttons, views) over and over again. With cross page copy/paste, at least you could just insert updated versions of your components instead of rebuilding them every time you want to use/update them.

2 Likes

Same, I have updates I’m delaying because of how long it will take me to manually recreate on a new page.

3 Likes

Not sure if I should add this here, or a different thread but being able to duplicate a table would be SUPER helpful as well - moving onto my 2nd customer application and need to create a table for children and separate table for grandchildren, fields are the exact same

Usually, when you need to do something like this it’s an anti-pattern.
Obviously your mileage may vary, but you might be better off creating a “children” link between the “people” and that way you can have infinitely deep links

The grandchildren then would be a lookup of the children’s children.

bumping this up again and adding my name to the list of users that would love this functionality. it takes SO much time rebuilding pages. and airtable has this functionality already and it’s glorious. but noloco has better looking ui and features so it’s like i’m solving some issues while introducing others.

1 Like