Looking for a better way to setup this interface so that it is more efficient. I’m currently using a list view to enter information to create a project estimate. In the photo, the user enters information for each workspace they are updating. There could be up to 15 workspaces but I don’t want to list 15 seperate sections on this view. I would rather it be setup to where the user would enter the data for the 1st workspace and if needed have an option to add a 2nd, 3rd, and so on but not have to show all 15 empty workspaces like shown. The 2nd part of this is when the estimate is emailed to the team, all of the workspaces are showing up as a grid whether or not information has been filled in. Optimally, I only want workspaces to show up if data has been entered.
Page 1 / 1
Hey @jennifer.barker!
Would you mind sending a screenshot of your current database schema (e.g. tables and fields)
As I see it, you might want to have Estimates table, Team Members table, Workspaces table, and one table (e.g. Estimate Line Items) which will be:
Estimate (linked) | Team Member (linked) | Workspace (linked) | Quantity (currency field)
On your Workspaces table you’ll have all 15 workspaces listed
On your Estimate Line Items you’ll have either 1 or 15 records created, where you will link the corresponding workspace as needed on each of such lines. Therefore if you have only 1 workspace for such estimate you will have only one line linked to Workspace 1. If you have 5 workspaces for such estimate you will have five lines, each linked to the corresponding Workspace.
If I’m getting your use case right, then this is fully scalable. If at some point in time you have yet an additional (16th) workspace, your estimates can be built without the need of creating additional fields (only additional records on the Estimate Line Items table)
Oh! And different question/answer is how you set up your interface for this. I personally like using Record Review pages.
You would create one record for each Estimate, and each detailed view of the Estimate (main panel of the page) will show a List view of the Estimate Line Items. You can choose to allow for inline Line Item creation and edits.
But once again, I might be getting your use case completely wrong.
With the new architecture you would only email existing line items in a grid view on your email.
Hmm, so the idea is to get data on each of these Workspaces, tied to a Project Detail record? I’m curious about how the data set up happens; are those 15 Workspace records created manually prior to someone coming to this page?
What if you put in a linked field to Projects <> Workspaces, which would let your users click into the Project Detail record then add new linked records as needed?
This assumes your tables are like this though:
Project Detail
Workspace Types
Projects <> Workspaces
re: The 2nd part of this is when the estimate is emailed to the team, all of the workspaces are showing up as a grid whether or not information has been filled in. Optimally, I only want workspaces to show up if data has been entered.
Hmm, how’s your automation set up for this? If you’re using a Find Record step for this, are you already filtering out records that don’t have anything keyed in?
