Just create a table in your database and then use a relationship to relate that table to a feature class. You people can make comments in the table. However, that will only work with Collector/Editors
I have done data driven pages and ReportLab in Python. Design formatting in both options is not fun. Images in both are also not fun.
Others I have seen are SQL report writer.
Thanks to all of you for sharing you experiences and suggestions.
I am intrigued by the Integromat workflow and will study the blog postings authored by the Survey123 team to see if this could work for us.
Well, that's a bummer! Thank you for confirming your suspicions.
Charging 2.5 credits per report export, which equates to 25 cents per report, reminds me of the days when color copiers first came out and we were charged 10 cents per page to print. Quite expensive.
OK, I'll look into Plan B; Robert and Doug's use of ArcGIS Pro and maybe ReportLab - Ugh
@JoeFlannery curious how you made out and what direction you decided on. Did you go with ArcGIS Pro? or something else?
Also, @PeterMacKenzie2 suggests that the on-premise version of Survey123 website (when it becomes available) is supposed to include the ability to run reports. However from my reading, there are some limitations that must be avoided to make this happen. But even if you are able to avoid the limitations, it seems like you still need to open your ArcGIS Enterprise to the public facing AGOL reporting service. Has anyone heard anything different? I would imagine that those who really could take advantage of such reporting (e.g. those like us that are looking to have report to support each asset inspection), would also be the type that have enterprise-wide data constraints that require all data to be stored on premise (or at least in-country - this is a Canadian organization). Any info you might be able to share would be appreciated.
A group within my company is using Survey123 with 30-40 fieldworkers on a large client project with sites across the USA. They have developed a stand-alone reporting system that does not use the S123 reporting system. I think they are using SQL Server Reporting System (SSRS) in some fashion. I am not in close communications with this internal group, so I cannot elaborate further. Even though the S123 report export credit cost went down to 0.5 credits per report, given the number of reports produced in a week, they had to come up with their own solution. Sorry that I cannot help with a more complete answer for you.