Latest Contributions by RPGIS

I am glad you got it working. In addition to your solution I am going to mark the one that I previously posted as well since both answers are technically solutions in terms of formatting but not in terms of the exact use case. I will make note to anyone else who has similar issues and comes across this post. ... View more

We ran into similar issues when trying to utilize views. The workaround we came up with is create a sql job that updates a database table referenced by the attribute rules.  ... View more

Do you have users actively editing and either not closing their sessions or have hanging edits? That can sometimes create locks which may be a reason. Try asking everyone to disconnect and then reconcile and post. ... View more

I didn't think to suspect that at all. You might be right and that could be causing the issue. If there are some attribute rules designed for feature to feature edits in conjunction with multiple users editing then that may be the cause. ... View more

Hi @RavindraSingh, Is the ultimate goal to have it so that you have a 1:1 corresponding updates so that when one associated record is changed then the other matching record is also changed. It might be easier for anyone to help troubleshoot your issue if you provide a clear expectation/outcome you wish to have. Example: I want the associated record with matching attributes in Tables A and B that update one another Table A has [x,y,z] fields and Table B has [a,b,c] fields Fields x and a have 123 as matching attributes and fields y and b have 789 as matching attributes The expected behavior is: When a record in Table A is deleted, the associated attribute in field a of Table B is set to null When field b of Table B is updated and the associated attribute in field y of Table A is populated, populate field b of Table B with the attribute found in field y of Table A You don't have to go into full detail but the more information the better. Sometimes drawing out the logic flow will sometimes help with situations like this. ... View more

This may resolve your issue but it is hard to say without knowing what common attributes exist between the two datasets. var lag = $feature.assetgroup var lat = $feature.assettype var lid = $feature.id var ML = FeatureSetByName($datastore, "Maximo_location") // Check 'ASSETGROUP = 16 AND ASSETTYPE = 0' if (lag == 16 ){ var F = First(Filter(ML, "maximolocationid = AND assetGroup == @lag")) if(TypeOf(l_features) == 'Feature'){ lid = First( l_features ).maximolocationid } } return lid var TblName = $feature.tablename var MaxLocID = $feature.id var ET = $editcontext.edittype var RelTbl = FeatureSetByName($datastore, "ElectricDevice") var l_edits = Null if (TblName == "ElectricDevice") { var T = First(Filter(RelTbl, "maximolocationid = @MaxLocID AND assetGroup = 16")) if( TypeOf(T) == 'Feature' ){ l_edits = [{ "className": l_tablename, "updates": [{ "objectid": T.objectid, "attributes": { "maximolocationid": MaxLocID } }] }] } } // Return edits to apply in ElectricDevice feature class if( ET == 'DELETE' ){ MaxLocID = Null } var V = { 'result' : {'attributes':{ id: MaxLocID } } } if( Count( l_edits ) > 0 ){ V['edit'] = l_edits } return V   ... View more

It seems like, correct me if I am wrong, that you are trying to filter object ids. This isn't recommended at all, specifically since object ids are unique to each record and can be hard to filter by. This could be causing your issue.  ... View more

So versions follow what's called a version tree, if you didn't know that already. What that breaks down to is that more versions equate to more delta tables. Delta tables are transactional states from the main parent table. You basically create a new state every time a version is created. With that being said, this can greatly increase the size of the database hence why it is recommended to compress the database nightly the more versions you have. The other thing is if you have multiple branch versions trying to apply edits then that can cause issues with reconciling data because to many edits can be applied at any given moment. The only other thing I can recommend is to set your rules to "Exclude from application evaluation" so they trigger server side and not in the application. If problems persist then try going traditional over branch and see if that makes a difference or try using vector tiles.  ... View more

If you're experiencing latency issues then you might need to try the following: Reduce the number of records returned by the service, as @MarceloMarques has mentioned. Too many records can result in poor performance. Set the display scale to a reduced scale. Too large of a scale can impact drawing as well as editing. You can try to publish the editing feature service to a reduced scale and publish a vector tile service at a greater scale. Reduce the number of editable versions. Recommendation is no more than 3. If cellular strength is a common issue, try publishing a traditional version. Branch versioning can work but is typically limited to the strength of a cellular network. In conjunction with publishing both an editable feature service and vector tile service, publish the feature service with only required fields and filtered values. Publish the vector tile service as needed. The methods mentioned above are the few methods that I'm familiar with regarding services in general. I can ask a few others for their take as well. @jcarlson @ChristopherCounsell @HaydenWelch @DanPatterson    ... View more

Then it may require you to configure your code so that if the sid is not null then filter the records, otherwise return, like so. var sid = $feature.site_id if( !IsEmpty( sid ) ){ var sitefilter = Filter($featureset, "site_id = @Sid") sid = Max(sitefilter, "ft_id")+1 } else{ Console('Enter a default value') } return sid Another option is to setup a NextSequenceValue which will automatically update to next value stored in the table. var sid = $feature.dacf_site_id if( IsEmpty( sid ) ){ sid = NextSequenceValue('dacf_site_id') } else{ return } ... View more

Try using the @ like the example below. "dacf_site_id = @Sid" @ references the value so if it is text then it will make it text, otherwise it will be any other value. The only other thing is potentially the field name itself. Try getting a list of field names to see if the field is called that or if you are trying to use an alias instead. ... View more

I did include the filter in mine to only look for those specific domain types but I think the issue was I set it to only filter to look for a number within the range specified. Isinstance() would have been the more appropriate approach. Isinstance is much better method so kudos on that. I wrote the sample script in a couple of minutes but had no means of testing it nor did I ask what your coded values were set to. list( set( [ d.name for d in domains for cv in d.codedValues for key, value in cv.items() if d.domainType is "CodedValue" and key in range(10) ] ) ) I am glad you were able to figure it out. ... View more

Your on the right track. The only thing you would need to do is set the FeatureSetByPortalItem for both feature and table and then create the featureset using values from both.  ... View more

You would be correct if the survey itself calculates based on another layer. Since the OP is looking to find which polygons intersect the survey points then @DavidPike is correct. If, however, the survey were set to get a calculation everytime a survey is submitted then arcade would work. ... View more