Currently, you must submit a survey to any newly published Feature Layer to gain access the "Data" tab of the S123 Website. This means you cannot upload a Feature Report template until something exists in the Feature Layer.
This order of operations is not always ideal when adding automations.
EDIT: I totally forgot about this one, but this also affects existing surveys that already have Feature Report(s) attached. If you do something that clears the database (e.g., add a repeat), you actually lose access to your currently existing Feature Reports. This is particularly annoying where automations exist. Essentially, you published the update > submit a record so you can simply access Feature Reports > have to deal with your automation potentially failing > update the Feature Report > deal with cleanup (failed automation runs, delete the pointless new submission, etc.)
Working with webhooks this frustrates me, I would be interested to hear the logic behind this requirement, and have it removed as a restriction.
Exactly. I feel like I am working backwards while setting up automations. I've set up enough at this point that you'd think I'd have gotten used to it, but nope lol.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.