There are a couple of issues that I have with my own implementation. However, it will hopefully serve as a starting point of conversation to resolve the overall issue.

1. I have added a getAllPages call on line 864 which fetches all the area JSON objects and saves them into a new Vue data variable called areaJSONList on line 100. I made this decision because the computed function responsible for filling the CustomTableComponent with the areas only has the area names. It doesn't have any other information (to my knowledge) that can help in distinguishing an area between being part of the greenhouse or being part of the field. Consequently, using the Seeding Input page as example, I decided to get the JSON objects to help me distinguish between the two.
2. The updateRowEditID (name change pending) on line 156 is incredibly inefficient in my mind. It's not noticeable when I'm testing it but filtering through the lists every single time we want to figure out if the seeding log being edited is a tray or direct seeding is wasteful of resources. A potential alternative that I though of is that after getting our response from the new getAllPages line added to the page, we can filter the areas into 2 new Vue data variables called (something along the lines of) trayAreas and fieldAreas and then the updateRowEditID simply figures out the log is a direct or tray seeding. Afterwards, either a computed or another Vue data variable could be saved with the needed areas and then passed into the computed method for the CustomTableComponent. After editing is done, this intermediary method/variable can be reset (if that's even necessary).
3. I don't really like that I had to remove the disableFilters call from the event handler inside the CustomTableComponent element tag in the Seeding Report. If someone could point me to some sort of resource that allows me to call both while still being able to pass the event's payload to updateRowEditID that would be much appreciated. I tried following some examples like this one but the event's payload wasn't going through.
4. There is no attempt to constrain/filter crops in this PR. There are seeds that are always planted directly into the ground and seeds that are always tray seeded. Is there something in the JSON object/some sort of crop information that details this? If not, should there be an issue opened to add this information? It might be worthwhile to amend the original issue (Seeding Report: Filtering Area Name Arrays Depending on Seeding Log #585) to simply deal with area for now and then create a separate one for crop filtering. Additionally, this will generate questions about the Seeding Input page. For example, if someone picks potatoes and potatoes are always direct seedings, then should we disable the radio buttons and only allow direct seeding information to be inputted? This is a conversation we should have with Matt.