Latest Contributions by LindsayRaabe_FPCWA

@KoryKramer thanks! ... View more

Hi Robert. Thanks for the link. Drom what I can see, this confirms I'm going about it the right way. We're using Arcgis Pro and the content is shared to a group that our Data Editors are members of with normal edit privileges. I anticipate that if this went the case,  they would be able to Append at all (been using ArcGIS Online for years now so across the majority of functions around groups and data sharing).  ... View more

@JonathanNeal Excellent. Looking forward to seeing it! Do you have a rough release date fort 3.1? ... View more

Further update: Apparently this process does work (with a tweak) as described here: Re: Change default split policy on new domains? - Page 3 - Esri Community ... View more

I'll have to give this another crack if I can find a feature service that still has the old settings. I think I did a mass run of updates when I had this working the first time so might not have any left. Suppose I could always try on a test dataset and see what happens. Good to know that it wasn't all in vein though! ... View more

Quite possibly that would work for us. We have similar workflows in a number of map templates anyway that do require a definition query, so All Rows would work the same as Visible Rows.  ... View more

I've just managed to confirm that it is an issue for ArcGIS Online Feature Services in version 2.9.3 but not shapefiles. It works as expected once we upgrade to 3.0. Now I've just got to diagnose a couple of other problems (confident they're not version related though) before I can get tall our users on 3.0! ... View more

So in lieu of finding a solution to this direct issue (of nested submodels and iterators), I came up with an alternate plan (that I believe works better anyway). I have now separated my model into the following 3 sections: Main Model (selects input data and parameters, fills out basic field calculations and gets the initial count of records from my 2 input datasets) OID Dataset 1   OID Dataset 2           1 Bunbury   1 Perth 2 Collie   2 Busselton 3 Manjimup   3 Kojonup 4 Albany   4 Geraldton       5 Kalgoorlie             Count = 4     Count = 5   Sub-Model 1 (inside Main Model which replicates the first dataset to match A*B (i.e. A=4 & B=5 then C=20) by repeatedy appending a copy of the input dataset to itself until it has 20 total records (5 times in this example)).  OID Dataset 1     1 Bunbury 2 Collie 3 Manjimup 4 Albany 5 Bunbury 6 Collie 7 Manjimup 8 Albany 9 Bunbury 10 Collie 11 Manjimup 12 Albany 13 Bunbury 14 Collie 15 Manjimup 16 Albany 17 Bunbury 18 Collie 19 Manjimup 20 Albany       Count = 20   Sub-Model 2 (also inside Main Model and NOT Sub-Model 1 like in my first attempt. This does the same as the 1st Sub-Model except on the second dataset, appending a copy of the 2nd dataset to the input dataset until it has reached 20 records total (4 times in this example)).  OID Dataset 2     1 Perth 2 Busselton 3 Kojonup 4 Geraldton 5 Kalgoorlie 6 Perth 7 Busselton 8 Kojonup 9 Geraldton 10 Kalgoorlie 11 Perth 12 Busselton 13 Kojonup 14 Geraldton 15 Kalgoorlie 16 Perth 17 Busselton 18 Kojonup 19 Geraldton 20 Kalgoorlie       Count = 20   The main model then sorts the first replicated dataset output by Sub-Model 1 by a name field which groups all spatially colocated features together in the table with new ObjectID's.  OID Unsorted >>>>> OID Sorted           1 Bunbury   1 Albany 2 Collie   2 Albany 3 Manjimup   3 Albany 4 Albany   4 Albany 5 Bunbury   5 Albany 6 Collie   6 Bunbury 7 Manjimup   7 Bunbury 8 Albany   8 Bunbury 9 Bunbury   9 Bunbury 10 Collie   10 Bunbury 11 Manjimup   11 Collie 12 Albany   12 Collie 13 Bunbury   13 Collie 14 Collie   14 Collie 15 Manjimup   15 Collie 16 Albany   16 Manjimup 17 Bunbury   17 Manjimup 18 Collie   18 Manjimup 19 Manjimup   19 Manjimup 20 Albany   20 Manjimup   It then joins it to the 2nd dataset by ObjectID. This join means that for each copy of a record in a group of records in dataset 1, it has a unique matching record from dataset 2. Field calculations are then done to preserve the attributes from dataset 2, the join removed and the final data exported to a new feature class.  OID Joined Dataset       1 Albany Perth 2 Albany Busselton 3 Albany Kojonup 4 Albany Geraldton 5 Albany Kalgoorlie 6 Bunbury Perth 7 Bunbury Busselton 8 Bunbury Kojonup 9 Bunbury Geraldton 10 Bunbury Kalgoorlie 11 Collie Perth 12 Collie Busselton 13 Collie Kojonup 14 Collie Geraldton 15 Collie Kalgoorlie 16 Manjimup Perth 17 Manjimup Busselton 18 Manjimup Kojonup 19 Manjimup Geraldton 20 Manjimup Kalgoorlie   Another small tip - use "memory " as the output location for working data instead of a .gdb (including %scratchgdb%) - it works so much faster! ... View more

Great idea. Simple, but the best ones usually are.  ... View more

Actually - just realised that this tip won't quite work in my case. The replication effect I'm going for isn't to match the total number of features already existing in Destinations, but what the total will be once Destinations are Replicated for each unique Origin location too (so a multiplying effect) which is why the Calculate Value is there at all (AxB = C) then test if B=C: false - add another lot on | true - stop iterating.  ... View more

Thanks for the tip - I'll look at implementing that on Monday. It makes sense to cut down as many steps as possible. As for python in place of iterators, I could do, but I'm far too novice to be efficient at it, and nobody else here has much python understanding so model builder is an easier solution to troubleshoot/fix should I not be around (in theory).  ... View more