Latest Contributions by TL2

I work in DEV, STG & PRD and am trying to determine the best practice.  So far my work flow is as follows: Create surveys in default 'My Survey Designs'. Once complete, push to DEV. Once pushed to DEV, copy entire folder contents and place in 'My DEV Surveys" Back in My Survey Designs, delete .itemInfo from each survey, log into STG portal and republish. Once pushed to STG, copy entire folder contents and place in 'My STG Surveys" Back in My Survey Designs, delete .itemInfo from each survey, log into PRD portal and republish. Once pushed to STG, copy entire folder contents and place in 'My PRD Surveys" Depending on which environment I am publishing in, I will bring in the appropriate folder contents. Does anyone have any thoughts or suggestions on this workflow?   When you delete the .itemInfo, not only do you loose the connection to the portal (good), but you also lose settings (bad) and I have to manually fix those. I have about 50 surveys, and will have hundreds soon.  Initially this will be a pain and is a bit clunky.   Thanks. ... View more

My issue is that the instance_name and the HFS both reference the name and not the label.  Because you can't have spaces I can't include someone's name in a instance_name without it appearing ugly (i.e. Joe_Brown).  This is the same when I bring in a HFS in arcmap.  It  does not bring in the coded domain labels, only the names. Arcmap is not as big of a deal.   What is the work around, I cant have a user enter his first and last in separate fields. Also, date cant be used in instance_name either. Thanks for all your hard work up to this point!  It's greatly appreciated! ... View more

I get the following error in my S123 Connect logs. error { "code": 400, "details": [], "message": "'originItemId' or 'destinationItemId' param required.", "messageCode": "CONT_0017" } Survey123 Connect stalls out with this... ... View more

We had a Server and Portal federated.  We created a new server machine and a new portal machine, federated and then replicated all the data.   So before we had Server1 (first machine) and Portal1 (second machine) Federated; and with datastore1 on a third machine. Now we have Server2 (fourth machine) and Portal 2 (5th machine) Federated (all server data and services copied over.   When I try and back up the new datastore(6th machine) pointing to Server2 and Portal2 I get this error: Error encountered: Backup folder '\\[folder location] is not owned by current data store. I have --bound false. Any suggestions.  Should I be able to do this? ... View more