Bring Back "Customize fields" in New Record Layouts

✨ Feature Requests
1

Would it be possible to bring back the “Customize fields” option in the top-right menu?

Customize

Currently, you open an existing record to edit/add new fields, which works fantastically.

The thing is, after using Tape for almost 3 years, I got used to clicking the “customized field” option in the top-right menu to add/edit fields in records. If it is not too much work, it would be nice to have it again, editing a “dummy/empty” record that updates all others.

2

Would it be possible to bring back the Developer Info on a per-record level?

Dev Info

I use this a lot when working with the Tape API. I think this one is more important to have than the “Customized Fields” mentioned above.

3 Likes
3

Hi @Luis,

thank you so much for your feedback, this is really valuable for us :100:

I understand your points about bringing back “Customize fields” in the top-right menu, and also the need for “Developer info” on a per-record level, especially for API work.

We’ll review both topics, check how they fit into the current “New Record” experience, and come back to you once we have a clearer direction and timeline.

I wish you a nice weekend.

Cheers,
Leo

3 Likes
4

I miss the record developer menu :cry:

  1. Open record
  2. Copy URL
  3. Paste URL into Drafts
  4. Copy Record ID from URL
  5. Paste Record ID were needed (probably postman)

Alternative:

  1. Open record
  2. unlock record view
  3. Make calc field with record ID in visable
  4. Copy Record ID
  5. Paste were needed
  6. Undo step 3
  7. Undo step 2

Last Alternative:
Build an automation
getRecordID

Please bring back the Record ‘Developer info’

In case it helps anyone:

View Screenshot
View Screenshot1200×1202 144 KB

2 Likes
5

Hi @Jason,

Thank you so much for sharing these insights from your side :100:
We’ll definitely take this into account for the next iteration toward the final release.

When we built the new record frame, we focused on getting into the fields fairly quickly, because releasing the full field scope is still a bigger blocker for many users and partners.
But we’ll definitely revisit these points and try to bring the most important developer workflows back in a thoughtful way.

Thanks again for the insights. It really helps us understand what was valuable, what was used a lot, and especially what our power users are genuinely missing!

Cheers,
Leo

2 Likes