Latest Contributions by RPGIS

Yes. Simply because tenants may vary but generally the building will have similar utilities and safety requirements. We have it setup so the building will primarily house anything regarding safety but the tenants will have their own unique attributes. Both the building footprint and tenant table schemas are nearly identical. This is to identify if a building is the same as a tenant or if it houses multiple tenants. It also keeps the data clean and easily configurable. The other thing to consider is, as tenants are vacated in multi-tenant buildings, then that may impact other workflows such as addressing, billing, etc. We are working to create a dynamic addressing system so that instead of maintaining points, instead we will use a tool that will derive the information from the attributes and construct temporary address points. ... View more

We had this exact conversation since I had been tasked with overhauling our preplan solution. We tried using the Esri solution, but that solution will only work if: You have clean data to work with or are starting from scratch You are not having to consolidate several datasets into a single working dataset The addresses, buildings, and anything else is updated in a timely manner The workflow we created is we built ours in house in our enterprise sde and are using the building footprints as the base working feature and have it setup in this manner: Building Feature/Footprint (polygon fc) Property Table The table is related to the building feature using a single numerical field The relationship created is a one to one Tenant Table The table is related to the building using the building id as the relational field The relationship to the building is a one to many ... View more

In this case then you wouldn't need multiple datasets but rather a single featureset to return a basic table of values to filter by. You would need to construct a basic featureset, like the example below, so that it only returns a single table of records. This will require fields to be manually specified for the new featureset table, and the attributes must map accordingly. function SetFields(N,T,L){ var b = 'esriFieldType'; var types = ['Integer','Double','String','Date'] var V = When( Includes(types,T) && T=='String',{name:N,type:b+T,'length':L} ,Includes(types,T) && T!='String',{name:N,type:b+T} ,Null ) return V } var Fields = [ SetFields('ExampleA','String',25) ,SetFields('ExampleB','Integer',Null) ] var Values = [] for( var row in somefeature ){ var attvals = {'ExampleA':'Something','ExampleB':1} Push(Values,{attributes:attvals} } var FS = FeatureSet(Text({ 'fields': Flds ,'geometryType': '' ,'features': Values })) return FS @KenBuja might be able to add to this in case I left something out. If you need to add a spatial component then you would simply need to pull that once. The configuration to add a spatial component has a similar structure but requires other spatial information to be returned. Here is a simple function for simply creating a union of multiple features, assuming they are the same geometry. function GetFSGeoms(InFS){ var Poly = [] for (var f in InFS) { var e=Geometry(f) ; if(!IsEmpty(e)){ Push(Poly,e) } } iif(Count(Poly)>0,Union(Poly),Null) } ... View more

Hi @TimTriesch1,   Do you mean to use the Grid Index Features Tool. You can specify size and everything which sounds like what your looking for.  ... View more

Hey @ChristopherCounsell, Have you tried overwriting the service or publishing a small subset of data to see if the lock has anything to do with the feature itself. Also, what kind of versioning is being used, if any, and does modifying the versioning fix anything? ... View more

Hi @MichielHorikx, There are plenty of solutions out there that can accomplish this. For starters, here is a link that shows the basic structure for editing other features. Advanced attribute editing In addition to that, depending on your workflow, here are some ways to go about. Attribute rule: you can setup a rule, if it is a feature in either sde or gdb If the layer is hosted: Use the field maps form to apply the same logic but used strictly as a form calculation If the edits are infrequent: You can use a simple field calculation and apply the same calculation but it is dependent on if the layer is either in an sde or gdb ... View more

So there are two ways in which you can do this: Editing Start and edit session Use the rotate tool to rotate it accordingly Using a field You can set a value, as a double, and set the polygon to rotate according to that value. ... View more

@KenBuja answer would resolve your issue. Just make that slight change and it should work. Another thing you can do so that your not needing to update multiple feature changes is to simply create an array of all of the sublayer ids/numbrer and loop through each one and push a new array with the featureset defaults Ex: var idarray = [27,28,30,31,32,34,35,37,38] var fsarray = [] for( var i in idarray ){     var id = idarray[i]     var nfs = FeaturesetByPortalItem(p, "c756ab8f4b654789812c1b9d6d783640", id )     Push( fsarray, nfs )     } ... View more

Hi @mward_dlc, It could be the case because it is a mobile dataset. One thing you can try though is if the same attribute expression will work as a calculation in Field Maps(if hosted). If it works locally in a file geodatabase but not in a mobile geodatabase then it is probably the limitation of mobile gdbs. ... View more

Like @KenBuja is saying. You are using $feature which is a single record. You instead need to use $featureset. ... View more

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