Latest Contributions by ChelseaRozek

Did you get the time calculations to work in the browser? I'm trying that same decimal time calculation for duration and it's not working in the browser but works fine in Connect ... View more

I just used this guide to add Open License Switcher (.bat file) from the .mxd context menu: https://www.howtogeek.com/107965/how-to-add-any-application-shortcut-to-windows-explorers-context-menu/ You could make simple bat files for Basic and Advanced with this help article: https://support.esri.com/en/technical-article/000011374 ... View more

This is great! Thanks so much for posting this! I was able to edit it to include our Standard licenses, and it's switching between them on my PC (Windows 10, ArcMap 10.7.1). The only issue is that it's not showing the Current Level and Current License Manager. Have you tried this on 10.7.1? Do you know what might be the issue? I don't see these values under HKEY_CURRENT_USER, but I do see ESRI_SOFTWARE_CLASS under HKEY_USERS. I've tried to swap out the KEY_NAME for this different location, but it's still not populating the Current Level and Manager. Update: I can get them to populate when I changed it to what's below AND ran the .bat as an administrator. I think non-admins are being blocked from viewing the registry values, which is weird that the bat can still change the values....    set KEY_NAME="HKLM\SOFTWARE\WOW6432Node\ESRI\License10.7"    set REG_LL_NAME="SOFTWARE_CLASS"    set VALUE_NAME1c="LICENSE_SERVER" ... View more

take a look at Ismael's example up in the blog post under "Adding previously entered data from your form". You can't directly put ${ImageText} into the bind column. Looks like you will have to make a ${watermark} row that will have something like concat(${ImageText},"&color=black&outlineColor=white&size=12") under calculation, and then just put bottomLeftWatermark=${watermark} in the bind column on your image row ... View more

Correct, as of now it can only be done through editing the JSON. It's not too tricky if you make sure to follow the syntax. Here's how to do it: - Click on the </> next to gear at the top of your QuickCapture project in the designer. Click Edit to edit the JSON. - If you want, copy and paste all the JSON currently in the designer to Notepad to have a backup. - Now you need to define the user input variable. Scroll all the way to the bottom of the JSON. There's a line that says "userInputs": [], our code is going to go inside the empty [ ]  - The main parts of the code are    1) ID (unique identifier, can be any text)    2) Label (shown above the input textbox in the mobile app)    3) Field Type (either esriFieldTypeString, esriFieldTypeDouble, or esriFieldTypeInteger)    4) Required (true or false; true means that the user must type in a value. It will exit the project if they try to hit Cancel to get past the prompt)    5) Domain (constrains which input is valid; value must be either range (numerical range), codedValue (predefined allowed values like Yes or No), or userDefined (can set an input mask, like 9999 would force user to input four digits))    (see screenshot below for what I did) - Then you just have to tell QuickCapture which field will use this defined user input variable. Search for the field's name. In my layer it's called casenum. By default, it said: { "fieldName": "casenum", "value": null } I changed the null to "${userInput:apple}" because apple was the unique id for the user input variable that was defined at the bottom of my JSON. Here's the finished section of my JSON with what I changed in yellow. You can leave inputMask null if you don't want to use it. Let me know if you have specific case number syntax and I can try to help you with the masking. A common JSON mistake is to leave a comma at the end of the last line within brackets. Notice "range":[] doesn't have a comma at the end when "codedValues": [], does. "userInputs":[all our code here], does because "version":0.1 comes after it in the greater { }. If you get an invalid JSON error, check for these commas or for a missing " " on your label, fieldType, id, etc. Note: I'm not using codedValues and range as I'm using userDefined as my type, however the JSON editor kept adding these lines back in automatically so I provided the full screenshot here so you wouldn't be confused. Since their brackets are empty [ ], this extra bit of code isn't hurting anything. When I open the project in the app, I am immediately prompted to enter a case number. Here you can see that the label value shows over the text box and the hint shows below it in grey. Once entered, the value will show at the top of the project where it currently says N/A so you know what is currently set and you can click the pencil to edit it. ... View more

Update: I believe the referrer IDs have changed. I'm being prompted to log in when using Collector and Explorer on these layers. I'm just going to use Jake's suggestion for now. One copy of the item shared publicly, limited to the URL where we host our web apps, and the other shared only to the organization and without any limit usage configurations set. This second one is the one we're using in Collector and Explorer as all the maps are only being used by organization employees and thus they'll be signing into the apps anyways. ... View more

Oh, I'm sorry, I thought that's what you were looking for. That's right, it only sets the maximum/minimum scale levels.  Setting the default view to Philly (in WAB if you aren't allowed to change the webmap) and constraining the zoom levels would make it very difficult for users to see Florida as they would have to manually pan down the eastern seaboard at the city level, and Florida would still be available in the attribute table. I'm not sure how to prevent users from panning in WAB. I haven't seen anything built in, so I imagine it would have to be custom. I have seen it built into the Minimalist template as "Disable all map navigation", though then you're missing all the widgets of WAB of course. ... View more

It looks like the only mobile apps they have are for Android and iOS: What are the requirements?—Workforce for ArcGIS | ArcGIS  You might be able to use the web app, but it wouldn't be as comfortable on a mobile device. ... View more

One more question, what's it look like on your hosted feature layer's settings page under Feature Layer (hosted)? Do you have any of the first 4 check boxed checked concerning editing? I tried replicating your situation: - I created a polygon feature class in a file geodatabase in Pro. Manually added a EditDate and CreationDate fields. - Published to AGO. When I checked "Enable editing", no fields were added. When I checked "Keep track of created and updated features" and "Keep track of who created and last updated features", it finally added the "automatic" fields, seen in yellow. Since I already had fields named CreationDate and EditDate, it named the new fields "_1" at the end. - When I edited in AGO, only the yellow fields automatically updated. This is because AGO knew these fields were to track created/edited features. The ones I manually made in Pro, it knew nothing about so it didn't autopopulate them. They just happened to be named "EditDate" and "CreationDate" but didn't have the intelligence behind them. So if your fields aren't autopopulating, I'm thinking they were manually created fields in Pro that happened to be called the same things as ArcGIS looks for. Since you don't have duplicates of these so named fields, your "Keep track of created and updated features" and "Keep track of who created and last updated features" may not be checked on. Not sure if you did this since I'm not sure if they're autopopulating correctly or not, but best practice (for Pro) is to "Enable Editor Tracking" on a feature class like this (see below). Otherwise, like I just mentioned, it can be done in ArcGIS Online. This will add all the needed fields and ArcGIS will know those are the ones it should be populating with the automatic values. Still not sure about the default value on the date field, I would try to change that to None if possible. ... View more

Indeed, that's how I usually use it, the automatically added and automatically populated CreationDate and EditDate fields. I can't even make those fields editable (via Configure Attributes) in a layer I freshly made in ArcGIS Online because you shouldn't be able to since they will autoupdate each time you create/edit features. No manual editing needed. Since you ARE able to edit these fields, I'm wondering if you have the automatically added CreationDate and EditDate fields from AGO in addition to these fields that you CAN edit that were probably made in the field geodatabase.  Tiffany Wu Can you provide this screenshot of your fields?  ... View more

That does seem strange. You said these were originally published from Pro, so they were created in Pro from scratch? Where did they originally live, a file geodatabase? Normally those fields are autopopulated with the creation or editing datetime when making/editing features in ArcGIS Online. I have never seen dropdown menus for them before. Is it a calendar picker or a text based one (like your original screenshot)? I'm wondering if these were custom fields instead of the ones added by ArcGIS. What is the field value type for them? ... View more

I hadn't tried it before so I just tested it out. I added the web version of my survey123 survey to a dashboard with the embedded content widget set to document. Is this what you did? I set up a quick Microsoft Flow flow: "email me when there's a submission". I submitted via the dashboard (not in edit mode) and I did receive an email. Tried it a couple times and it kept working. Did you do anything differently? Is this the first time you tried doing it, as in has it ever worked for you? ... View more

On the Map tab in WAB, go down to the button in the middle of the panel that says Customize... for the Customize Visible Scales menu. In the popup, you can delete which scales you don't want shown in your WAB app. I usually delete the 6 or so top ones so users can't zoom out to the whole US or world since everything I do is only on the county level. Above that button (on the Map tab), you can set the default extent to make sure they start on the correct view you want. They could technically still pan over to Florida, though that's unlikely since it would take forever since they won't be able to zoom out all the way. ... View more