Latest Contributions by RichardLittlefield

Yep, this solved the issue. Just had to clear the cache after making this organizational change. Then everything worked. Thanks! ... View more

Any updates? I'm experiencing the same thing. If I open to view the experience builder site, it just "spins" and never opens. If I try and edit the experience it just spins on the loading page, never opening up to the experience editing page. This is on a PDS site as well, but broke with last weeks AGOL update. Seeing this in both Chrome and Edge browser. ... View more

I agree this would be such a great improvement to be able to call out dynamic text through a relationship.  I have a map series for a Sign Inventory. The way this inventory is done is there is one feature class for the Assembly - this is the pole for the signs. It could be a post or the overhead assembly that signs hang from on a highway/interstate. I have another feature class for the Sign. This is a point for each sign on the assembly. The assembly have the field photos, while the sign feature class doesn't allow attachments. I end up giving each feature class unique ids and also populate the sign feature class with the closest assembly id. I then build a 1:M relationship between the assemblies and signs. In the map series I create blocks or sections for each piece of information. So at the top of the page I start with the assembly information. Then create sign blocks of information for each sign. So depending how many signs on an assembly depends how many sign blocks there are. To be able to get the sign information on the assembly map series I work around the dynamic text limitation by exporting the signs to a table and after some data formatting join them to the assembly (permanent join (join field)). This can make the schema extremely long, however it's my workaround. Being able to show dynamic text of attributes from the relationship would be extremely helpful and save a lot of time. I guess with many records, there would have to be a way to sequentially grab/call that particular attribute in a sequential order every time. I'm also showing the field photos that are related to the assembly in my map series. I have created map series using table frames and related data before, so I'm well aware of that workflow. Basically would like to do the same, but with dynamic text attributes. In my example above, I have too many fields to be able to show that information through a table. That is why a sign section/block is used. Please add this idea to map series.  ... View more

No never heard anything. Since this post I've changed jobs and haven't really been following what's available in the Windows platform. I remember hearing officially that they were going to bring Field Maps to Windows, but don't know if that's actually happened. I have no idea about Workforce. ... View more

Has anyone figured out a solution for this? I'm experiencing the same thing now, so doesn't seem like this has been fixed. I published a survey from Connect (version 3.16) to AGOL. The row in my excel sheet is a file type with appearance as multiline. Then a constraint of count-selected (${field_name})<=10. This limits it to a maximum of 10 files. When testing in Survey123 Connect, it works great. I can attach multiple files, up to 10. Just as intended. Then I publish to AGOL. When I go to the survey on AGOL (web form), it only allows me to upload one file. I can't do multiple files. The Survey Settings is set to 'Use the version the survey was published with (3.16).' I'm also using this survey in an experience builder app and same thing, it only allows you to upload one file, not multiple. I did remove the constraint and that fixed the issue. It allows for multiple file uploads across all products. However there isn't a file limit now, so end users could upload many files, which isn't ideal. ... View more

Learned something new today. 😊 Thank you @BernSzukalski ! This was exactly I was looking for. I curated the gallery for all of my groups and it worked perfectly. Now all of my end users will hopefully stop clicking the wrong application and be forced to start with the proper one.    While trying to google this solution, I guess I was using the wrong terms. I was trying to search for the content settings or recently added content that are either on the overview page or in the group settings. Switching the group to the curated content, changes the language on the overview page to 'Featured group content'. If I knew that, maybe that would have helped my searching. Either way, thanks again Bernie! I'll most likely use this setting for all my future group creation moving forward. ... View more

Thank you Jasmine! Turing the fields to read only was the solution. Glad to see you with the solution 🙂 ... View more

This may not be what you are looking for, but maybe a helpful solution. There are Domain to Table and Table to Domain tools. These might be helpful to you. You could use these to export to excel. Make any changes and then import back to a new domain. Or export for for whatever your purpose is. Once a domain is a table you can use the Table to Excel tool to get your spreadsheet. When you are in the domain view in Pro, you can also copy/paste the entire domain. This is great for copying the domain from one database to another.  Hope that helps! ... View more

I think Attribute Rules should be supported in ArcGIS Online as well. They can be so powerful and being able to rely on them in ArcGIS Online is key. These days it seems most people's workflows eventually are publishing data to AGOL either for viewing or data collection. AGOL is integrated so well into Pro now, that you would think we could do this by now. Attribute rules can keep your data integrity, so collecting data with AGOL (field maps, survey123, etc.) you would expect to be able to keep that same integrity as you could in Pro. It's unfortunate you can not. I'm personally building a database project and wanted to use experience builder and possibly survey 123 to enter new table records in  tables with relationships. I was very excited to get attribute rules working with populating unique ids automatically and populating fields based on other fields automatically, only to be disappointed that I can't use the rules outside of Pro. What a disappointment. This idea has been on here for years, and still isn't in an implementation plan, so who knows if it would ever happen. I'm assuming Utility Network and Parcel Fabric use attribute rules heavily. My understanding of those if you have to edit those from a feature service (either hosted/rest), so I wonder how those work. Can you not edit those in AGOL? How does the system keep the attribute rules if you were to put your UN/PF on AGOL/Portal? Which I thought was mandatory, I thought you have to edit it's service and cannot connect directly to the database. ... View more

Add a new row to a non-spatial table is a must. Please add soon. ... View more

I was in a similar situation. Using Attribute Rules to create an id, however didn't need the concatenate. The Text(Sequential Number, '0000') worked perfectly for adding leading zeros to your unique id with arcade expression in the attribute rules. Thanks! ... View more

I agree. We need to be able to view the database sequence the same way we can see domains or tables/feature classes inside a file geodatabase. Not being able to see this makes it extremely difficult to know if they are being used or not, or even remembering what you named the sequence. Being able to see it is a much needed improvement. Please implement this in a future release. Also being able to edit it would be helpful as well. If you are using it in an attribute rule to automatically number your features. What if you need to delete some features and would like to then manually update your sequence to start at where the edited features left off? Looks like you can now view the sequence with python, however I'm not a python person by any means and I'm having issues trying to get the python syntax to successfully run. Not everyone knows python, so being able to see these sequences in some sort of viewing either through a table or similar to the domain view would be extremely helpful.  ... View more

I agree. We need to see all values when building select by attributes. Not all data is perfect and follows a domain, so when reviewing data seeing all values is extremely helpful. The 'Select Only Invalid Objects' option in the Attribute pane is helpful and a nice improvement, however I still think being able to see all values in the select by attribute window is a need. That's the point of 'select by attributes', you want to be able to select by the attributes in the attribute table. Not showing all values because it isn't in a domain isn't allowing you to fully select by attributes in my opinion. To me that makes to tool incomplete. It seems like extra work to run a frequency on a field in your table, than use some of those values in a SQL statement to select by attributes, when that could be accomplished much quicker by showing all values. ... View more

Thanks Aubri. I ended up creating annotations feature classes for each scale and then setting up page queries. Worked really nicely. I looked at the various scales and realized I probably had about 30 different scales, so it wasn't too bad setting up. Just time consuming going through each page and setting up. ... View more