I am building an Experience Builder on a self-hosted feature service with multiple related tables. We are building a directory, so there are multiple related tables and features.
Agency table has Programs as children
Programs have services as children
Services are features with locations.
I'm trying to set up an test editing Experience for the person who will be maintaining to try out the workflow. This has to be fairly simple and intuitive to go through for the user.
I am debating between setting up two tabs (1. Edit existing data, 2. Create new data) versus allowing everything to be done on a single page. The answer to this will probably boot this into the two tab category.
I have the agencies set up, and selecting an agency filters a Programs list below it. Selecting a program filters the services.
When creating a new service, I want to know if using the Editor widget allows me to auto-populate a new service with the related Program GUID? I don't want to have to put instructions for the user to copy/paste the GUID from a previous step if I can avoid this by having it auto-populate. Really trying to avoid error opportunities here. I know I can do this with Survey123, but I am testing out the Editor widget first and would like to know if this is an option between two related tables or a related table and a feature service.