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

Handling create related record/feature directly from Manager app #944

Open
azizaparveen opened this issue Oct 9, 2024 · 2 comments
Open
Assignees
Labels
Milestone

Comments

@azizaparveen
Copy link
Collaborator

Describe requirements

We need to think about how we can handle related record/feature directly from Manager app. Here are some ideas came from Chris and Sarah

  1. We can make it easier to connect parent feature from the related record/feature
  2. Restrict related table/layer visibility as an independent table/layer

Alternatives

No response

Other Relevant Info

No response

Impact

No response

@azizaparveen azizaparveen added the 2-ENH New feature or request label Oct 9, 2024
@azizaparveen azizaparveen self-assigned this Oct 9, 2024
@azizaparveen azizaparveen added this to the 2025.R01 milestone Oct 9, 2024
@azizaparveen
Copy link
Collaborator Author

@chris-fox @sarahmcdonald7
I am leaning towards restricting related table to show as independent that can be navigated to Chris I remember you talking about this that since we can add related records through parent record, adding the capability to create new record in related table is redundant and may need more work on the development side. I agree with your opinion.

Please let me know your thoughts on this

@chris-fox
Copy link
Collaborator

@azizaparveen, My opinion would be that we don't do anything special for related tables in this regard. Instead I think we should implement the feature described in this issue: https://devtopia.esri.com/WebGIS/arcgis-template-configuration/issues/4721.

If we implement that feature users can choose to disable related tables from showing in the dropdown and as a result not allow them to view, edit or created records in the table directly, only add or edit via their parent record. This is the approach I would take.

Leaving it as is, would be consistent with the Map Viewer as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants