When you use a Notion button property to duplicate a database template, the resulting page may miss certain blocks, contain broken formulas, or fail to carry over linked database views. This behavior occurs because the button property duplicates the template page at the moment the button is clicked, but the template itself may contain dynamic elements that the duplication process does not fully resolve. This article explains why the button property fails to duplicate templates correctly and provides the exact steps to fix the issue.
Key Takeaways: Fixing Duplicate Template Issues with Notion Button Property
- Button property > Edit Button > Template: The button property uses a template block that must be manually configured with all desired content, not the database page template.
- Database page template vs button template: The button property ignores the database page template entirely — it only duplicates the content you place inside the button’s own template block.
- Replace dynamic references with static text: Formulas, rollups, and linked database views often break during duplication; replace them with static text or simple properties before adding them to the button template.
Why the Notion Button Property Fails to Duplicate Templates
The Notion button property is designed to perform an action when clicked, such as creating a new page in the database. When you set the button to duplicate a template, it does not use the database’s default page template. Instead, the button property has its own template block that you must populate manually. If you leave the button template empty or assume it will pull content from the database template, the resulting page will be blank or incomplete.
The root cause is a misunderstanding of how the button property handles duplication. Many users expect the button to duplicate the database template that appears when you manually create a new page. But the button property creates a page using only the content you define inside its own template editor. This means any blocks, properties, or views that exist in the database template are ignored unless you explicitly copy them into the button template.
Another common cause is the presence of dynamic elements like formulas, rollups, or linked database views. The duplication process may not evaluate these elements correctly, resulting in broken references or empty fields. For example, a formula that calculates a due date based on the current date may show an error in the duplicated page because the formula tries to reference a property that was not carried over.
Steps to Fix the Button Property Duplication Issue
Follow these steps to ensure the button property duplicates the correct content. You will need to manually configure the button template with the exact blocks and properties you want in the new page.
- Open the database that contains the button property
Navigate to the database view where the button property is located. Click any page to enter it, or open the database as a full page. - Locate the property column that contains the button
Scroll to the column that holds the button property. If you have not created the button yet, add a new property and select the Button type. - Edit the button property settings
Click the property name at the top of the column. In the property settings panel, choose the action type. Select Create a new page in this database and then choose the Duplicate template option. - Open the button template editor
After selecting Duplicate template, a new section labeled Template appears below the action settings. Click the Template area to open the inline editor. This is the content that will be duplicated when the button is clicked. - Copy the desired content from your database template
Go to your database settings by clicking the database name at the top of the view. Select Templates from the left panel. Open the template you want the button to duplicate. Select all blocks in that template and copy them using Ctrl+C or Cmd+C. - Paste the content into the button template
Return to the button property settings and click the Template area. Paste the copied blocks using Ctrl+V or Cmd+V. The blocks now appear inside the button template. You can rearrange or edit them as needed. - Replace dynamic elements with static alternatives
If the template contains formulas, rollups, or linked database views, replace them with static text or simple properties. For example, instead of a formula that shows the current date, type the date manually or use a Date property with a default value. For linked views, consider using a simple text block that describes the view instead of embedding the actual view. - Test the button
Click the button property in any row of the database. A new page should appear with the exact content you placed in the button template. Verify that all blocks, text, and properties are present and working.
If Notion Still Has Issues After the Main Fix
Duplicated page shows blank or missing blocks
If the duplicated page is empty or contains only some blocks, the button template may not have been saved properly. Open the button property settings again and check the Template area. If it appears empty, repeat steps 5 and 6. Also ensure you did not accidentally paste into a different database or page.
Formula or rollup properties show errors in duplicated page
Formulas and rollups depend on other properties in the same page. If those properties are not included in the button template, the formula will break. In the button template, add all properties that the formula references. Use the Add a property option inside the template editor to include each required property.
Linked database view shows stale or no data
Linked database views in the button template will not automatically refresh when the button is clicked. They show the state of the source database at the time the template was configured. To fix this, remove the linked view from the button template and instead insert a simple text block with a link to the source database. Users can then open the source database manually to see the current data.
Button property does not appear in the database
If the button property column is missing, you may have deleted it accidentally. Add a new property and select the Button type. Configure the action and template again. Note that button properties cannot be hidden from a view — they always appear as a column.
Notion Button Property vs Database Template: Duplication Behavior Compared
| Item | Button Property Duplication | Manual Page Creation (Database Template) |
|---|---|---|
| Source of duplicated content | Button’s own template block | Database template selected in Templates settings |
| Supports formulas and rollups | No — may break during duplication | Yes — evaluates correctly when page is created |
| Supports linked database views | No — view shows stale data | Yes — view updates based on source database |
| Requires manual content setup | Yes — you must paste or type content into template block | No — content is predefined in database template |
| Can be triggered from any row | Yes — button appears in each row | No — user must click + New or use a keyboard shortcut |
The button property is best for creating pages with static content that does not rely on dynamic database features. For pages that need formulas, rollups, or live linked views, use the database template and create pages manually.
You can now configure the button property to duplicate templates correctly by manually populating the button template with static content. If you need dynamic elements, consider using the database template instead of the button property. As an advanced tip, you can combine both methods: use a button to create a minimal page with static content, then add a separate automation or button inside that page to pull in dynamic data from other sources.