Working on a project for adding new entry/entries to a table and/or viewing the table.
We have required fields for adding a new entry. Only one of those fields is required for viewing. The expectation is that when the user selects items from the dropdown fields, a table will display with those filters. The user can then click an "Add" button to add a new entry to the displayed table as long as they filled out all the required fields.
This image is actually an interpretation because I added on the "View" button. Initially, it only had the "Add" button. I suppose they want the table to start displaying and filtering results as the user makes their selection.
I don't think it's good UX, or even good practice in general to make these form fields do double-duty. (Is it even technologically feasible to allow the fields to act both as filters on a table, and data for an entry?)
My solution is to separate the View/Edit from the Add as two separate features. They want them on the same page, which would cause us to have to include these form fields twice in the same page, but for different purposes. Other applications I've worked on have separated these functions entirely into separate tabs or pages, but I can see why in our scenario a user might want/need to see a table while or before adding a new entry.