Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

COJO blank as base table and from CO and COG when using default COJO view #6146

Open
melton-jason opened this issue Jan 23, 2025 · 0 comments
Labels
2 - Forms Issues that are related to the form system geospecify

Comments

@melton-jason
Copy link
Contributor

melton-jason commented Jan 23, 2025

Extension of #6040
From #6047 (review)
Somewhat related to #6143

Describe the bug
This is technically a feature request, but I labeled it as a bug because I think it might be fairly common to add cojo to any existing views for CollectionObject or CollectionObjectGroup without explicitly specifying the CollectionObjectGroupJoin_Sub view.

@specify/ux-testing, do you think the case would be very common?

To Reproduce
Steps to reproduce the behavior:

  1. Go the DataEntry form for a new CollectionObjectGroupJoin
  2. See the form is blank

This works as a fix for the common case for now --- viewing a COJO from a related resource.
Although, the problem still happens when directly viewing the COJO.

Screenshot 2025-01-08 at 10 10 24 AM

From #6047 (review)


  1. Go to the form definition for CollectionObject or CollectionObjectGroup
  2. Add cojo to the form as a Subview (or QueryComboBox, but beware of Changes to new dependent resource from Query Combo Box not initially saved #6058)
  3. Specify a viewname which points to a view using the default CollectionObjectGroupJoin view
    a. If viewname is ommitted, Specify will automatically use the view with the related table's name (CollectionObjectGroupJoin in this case)
  4. Go to the respective DataEntry form for a new record of the modified view
  5. Add a new CollectionObjectGroupJoin
  6. See the form is blank
blank_cojo.mov

Expected behavior
Ideally, I think we should show something for the CollectionObjectGroupJoin form when there is no child CollectionObject or CollectionObjectGroup.

An easy fix would just be to update the form definition to at least include both the childCo and childCog when both are empty: when one is set, the other condition would take precedence and update the form.
Business rules should still prevent the user from saving a COJO with either no childCO and childCOG, or both a childCO and childCOG.

From #6047 (review)

Please fill out the following information manually:

  • OS: macOS Sonoma (14.3)
  • Browser: Google Chrome 131.0.6778.265 (arm64)
  • Specify 7 Version: production - 0c9839d
@melton-jason melton-jason added 2 - Forms Issues that are related to the form system geospecify labels Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2 - Forms Issues that are related to the form system geospecify
Projects
None yet
Development

No branches or pull requests

1 participant