Latest Contributions by RPGIS

You would need to write an arcade expression in order for the symbology to change dynamically, especially for a date field. Something like the example below should work. var dt = $feature.InspectionDate iif( !IsEmpty(dt) && Year(dt) < Year(Today()), 'Not Inspected', 'Inspected') // if you plan on using multiple years if( !IsEmpty(dt) ){ When( Year(dt) == Year(Today()), 'Current', Year(dt) == Year(Today())-1, 'Last Year', Year(dt) == Year(Today())-2, 'The Year Prior', 'Old') } ... View more

Yes, the constraint rules can run for both client and server side. As perhaps mentioned before, client side simply means using the devices resources to check for edits whereas server side typically checks tables where attributes reference other tables. For instance, Field personnel update an inspection record n field maps. // Constraint type on client side var dt = $feature.date iif( IsEmpty( dt ), { 'errorMesssage':'Please update the date field'}, True) // Constraint type on server side var FieldMapAtt = $feature.SomeValue var RelVal = Filter( FeatureSetByName($datastore,"Feature Name",['Field'],False), "FieldName = 'SomeValue'" ) iif( TypeOf( RelVal ) != 'Feature', False, True ) Hope this gives some idea on how this will work for you. ... View more

So the way attribute rules work is similar to sql triggers. Because of this, any edits done to a record will trigger some kind of response if one is set. Validation simply checks to see if any of the incoming edits do not meet a certain criteria and can either warn or flag for certain issues. This won't keep the data integrity if that is of more importance. Rules, either constraint or calculation, will best serve your needs. The other thing, regarding rules, is that they can either be application dependent, such as the case with most offline use, or that can be set to server only. Meaning when an edit is applied, if client side, it will only run on that instance whether it be tablet or phone, but if it is server side then it will update via the server and return the change after it passes server side. Server side is typically used for checking against other tables/features or the features base table that would require the change be pushed to the server. It is then checked for changes either applied or attributes pulled from the other features, applies changes, and then returns and changes to the version used by the field. ... View more

That actually makes it the easiest since the latest version of Enterprise actually allows for better control using attribute rules. So to get to the rules themselves: You can either right click on the table/feature in the catalog and select Data Design or similar to the image below From there you can click on the attribute rules Click on the constraint tab and you can then add your rule. ... View more

Hi @CodyPatterson, It is possible to do so. The way to go about it is to add a constraint rule on the attachment table itself to look for the globalid of the related feature record and then set the insert trigger to have it look to see if the required attributes have been filled out. ... View more

Hi @Steve_Walker, If your using a referenced feature service and you want to publish the new changes then you won't lose any of the information. If it is hosted, then what you will need to do is copy/modify the collected data into the pre-existing local feature class, modify the domains/fields/etc. and then republish as to overwrite the data in AGO. ... View more

Hi @Ammarali, Just to clarify, are you asking as part of an idea from Esri or something else. If it is an idea then this can be moved to the ideas page. Also, if it is an idea, then please provide any supportive reasons so there is a stronger likelihood that if it can be implemented for multiple people then it can be made as part of an update. ... View more

I am not sure because we use attribute rules to dictate a lot of the editing behavior. It may automatically populate but I cannot be certain of that. In any case you may want to consider using an attribute rule just to be on the safe side. ... View more

Hi @aam, So to answer your questions: Yes, you can append data to the related table using information from the parent table. We have attribute rules that do this automatically for our inspections. You can use any kind of id but you must make certain that the field data types are the same and the primary key fields in both tables are of similar size. So yes you can use GlobalIDs. Just make sure the related table has a separate globalid field that isn't auto-populated. Yes - Must be a global id When you append and you field match accordingly it will match automatically. You do not want the related table to populate automatically because your relationship will not work. The relationship is looking for identical values so if they are different then it will not work. ... View more

Hi @yockee, I don't typically use validation rules simply because the workflows that we have generally will account for all the edits that come in from the field. Typically validation is mostly for verifying that the data that is entered meets a certain criteria. It is usually best to create calculations that will account for certain things rather than try and force the editor to fill in the information. The solutions that we have created automatically account for certain behaviors and so there isn't a need to for validation. The other thing is if you are concerned with certain types of edits then you could try and create a constraint rule instead. The benefit of a constraint rule is that you can customize messages will appear to the editors and letting them know what needs to be corrected in order to continue editing. ... View more

There is but it may require some knowledge of either arcade or python in order to find unsnapped points. The other thing to try is to set a location filter for all the points and finding the nearest line where the distance is greater than 0. ... View more

Hi @Jennifer_Parmeley, To Clarify, just so others can get a better understanding of what you mean, do you mean to add the ability to freeze fields so users can still see the fields as they scroll. The other slight workaround is to zoom out of the webpage but that will result in the text shrinking throughout. I think the ability to freeze fields/column headers would be a more straightforward improvement. ... View more

So there might be a few things that can be tested. Create a hosted view that is updated in field maps but has a filter set in the map to only display certain values. This should restrict the editing of the related record You can simply filter out the table values so that they are only visible in Survey123 but not in field maps Append a value to the related table such as a text field with attributes stating "survey" and have it so that it does not display in field maps when you set the visibility fields to look for fields that don't have that value.   ... View more

The only thing I can think of is to create an expression that concatenates and modifies the html at the same time. Something like: var C = ['• SomeValue','• SomeValue','• SomeValue'] return Concatenate(C,'/n') in addition to the html element. Something that may be doable but I have yet to test this fully. ... View more

So that is a fairly simple and straightforward method but it does have a strange workaround. Basically you would simply need to set a pre filtered field to only show the actively edited features. If you need further guidance in pretty sure others in the community have also handled this as well. ... View more