Latest Contributions by AndrewZimba1

Got it now...  human error (of course).  Thank you for all your help.  This has been extremely instructive.  Are there any resources that could help expose more of the capabilities of attribute rules?  For example, the update of attributes with the edit.[] block is not something I would have even known was possible from the examples shown in the Pro documentation. ... View more

Right on.  Now it seems that will enforce the attachment type, but it won't enforce that a point must have an attachment, right? ... View more

Hmm.  yes, it definitely exists.  It's the same polygon field that is contributing the SampleID from the previous rule (which works great, BTW.  TY!!).  I'm very confused as to why it's not finding it.  I would think if it didn't exist it would throw an error on line 1 and not validate.   ... View more

Close, but running into a problem here.   This is my implementation. var fsBuffer = FeatureSetByName($datastore, "Section3.DBO.PlannedSoilsSamplngLocationBuffers", ["GlobalID"], false); var intersectPolys = Intersects(fsBuffer, $feature); var fsBufferFeature = null; for (fsBufferFeature in intersectPolys) break; if (fsBufferFeature == null) return $feature.GlobalID; //we found a polygon feature set its HasPoint to Yes return { "result": $feature.GlobalID, "edit": [ { "className" : "Section3.DBO.PlannedSoilsSamplingLocationsBuffers", "updates": [ { "GlobalID": fsBufferFeature.GlobalID, "attributes": {"SampleComplete": "Yes"} } ] } ] } and this is the error I get: I think I am mis-interpreting your $feature.field syntax. What field in the point feature class should this rule be attached to?  It looks like the only field available is SampleID (the one that is auto-calculated from the previous rule). BTW, how do you insert that nice code block into the posts? ... View more

This is very helpful indeed Hussein!  Thank you so much.  I'm attempting to implement now. ... View more

I may have spoken too soon.  For the polygon-attribute-flipping when it contains a point from another fc, it is the *point* that is being created/updated, not the polygon.  So we have sample areas polygons that are existing, and when a sample point is taken it get's the ID from the polygon.  We then need to simultaneously trigger the polygon to update its hasPoint field to "Yes" since it now contains a sample point.  I hope that makes sense. ... View more

BTW Hussein, this is probably a big enough and useful enough topic that you could write a very successful book on the subject.  These tools may finally give us the ability to build out Collector apps from the desktop that are on par with ArcPad wrt data validation and conditional attribution. ... View more

This is perfect Hussein.  Thank you! I do sheepishly have to say I did think of another attribute rule application question over the weekend.  I'll post that in a separate thread as it's slightly different in scope (I think). Your assistance has been extremely helpful.  Thank you again! ... View more

Perfect.  Thank you for all your help.  One more for the road: How could I turn this script inside out and say "If a polygon contains a point from a specific fc, calculate a field attribute in the polygon fc to 'yes'"? ... View more

Thanks again Hussein!   Quick clarification on the gdb.DBO thing - this rule is designed to take effect when other users add points to the FC thru Collector.  Since they aren't owners, do I need to explicitly put in the gdb.DBO, or is it only when authoring the rule where that applies?  In other words, once the rule is "in there" since I put it in and don't need the gdb.DBO, will it evaluate correctly when others insert points? ... View more

Thank you Hussein!  It looks like I had to get the FC name in there without the gdb.DBO. prefix AND get the field name containing the attribute in there to get it to recognize the table. The expression now checks as valid.  HOWEVER, when I go to save the "Applying changes" progress bar just rolls and rolls. Do these attribute rules have to be applied before services are published from these feature classes?  Does versioning/archiving have to be off?  Any details like that I should be aware of? ... View more

Hi!  We have a portal implementation for a project which, when active, we expect between 175 and 300 named users to access continually for up to 12 hours/day.  is there some sort of tool with which we can simulate this level of usage to determine infrastructure sizing necessary to support? ... View more

Any action on this?  Last reply was three years ago.  As far as I can tell, conditional logic is all that needs to be implemented to have collector completely replace ArcPad.  Russell, please contact me if you would like to discuss why this is so important. ... View more