1. What is the problem? Be very detailed.
In Aggregate, we used to have a username/password style user creation, which allowed for remote deployment very quickly, and did not need the data collectors to have Collect installed before handing out user/pass data to the field staff. Now, using Central, it seems the preferred method is creating an App User and doing a QR Code scan. The QR Code seems to be the only way that a Collect App can be tied to the form. Is there a way make users in the same user/pass format in Central, that we used to have earlier in Aggregate?
2. What app or server are you using and on what device and operating system? Include version numbers.
Central from master brank of Git and Collect from Google Play v1.28.2
3. What you have you tried to fix the problem?
I didn't find any resolution yet
4. What steps can we take to reproduce the problem?
Make a new install and new app-user, and try making user/pass, doesn't work.
5. Anything else we should know or have? If you have a test form or screenshots or logs, attach below.
As far as I'm aware no, you aren't able to access Central from Collect with a username/password. Users with a username/password on Central (web users) have access to Central itself but it is not intended that you'd use those account to submit forms.
Is there a reason the QR code isn't working for you?
I hear you that QR codes are most convenient for centralized configuration or configuration at an in-person training. If your staff is entirely remote, you can send a QR code via another communication channel you have such as WhatsApp. Right click on the QR code in Central to save it. Alternately, if you would like your staff to have other settings set, scan the QR code into one of your devices, configure that device like you want (e.g. hide some of the main screen buttons, change the font size, etc), and then save the QR code to your device to send to your staff.
If your staff will be getting together in person, you only need to send the QR code to one person who can display it on their device while others scan it. You can also send it to every staff member who can use the "Import QR Code" action to select and load the image (see documentation).
Thank you @LN for your reply.
The problem with this approach is, is there a way of bulk extraction of QR Code data?
In user/pass method, all we would do is pass on the user/pass table to the respective field offices, and they would disseminate the data to the field officers. What would you suggest for QR Code?
I should have asked you for the high-level problem you're trying to solve. I answered for scenarios where App Users represent roles but certainly accounts can also represent individuals. How many field offices do you have and how many different users are you provisioning at each?
Is there anyone at the field office who could be granted access to Central? They would need to have a Project Manager role to have access to the App User list but they would not need to have a sitewide role. If it's not acceptable for them to be project managers, perhaps they could be granted that role temporarily at the beginning of the project. Then they could either display each QR code for a field officer to scan or send each QR code to the correct officer.
If that doesn't work, you could do a bulk export but it currently requires scripting to fetch different App Users' auth URLs, generate the corresponding QR code, and organize them in one document per office. This is something we could provide a sample for but you would need to be comfortable running a Python script.