POST
|
Amir Bar-Maor - the "enable undo" function of the #append tool is not available when used inside of a #arcgis pro task .
... View more
02-13-2019
10:53 AM
|
0
|
0
|
1598
|
POST
|
I'm using #survey 123 connect v3.1.113 For your first point - I create my own GeoPoint in Survey. The purpose of my workflow is to audit check the point collected in "the other" feature service. So I compare the location of the two points back in the office. As for the second question - yes, it needs whatever value you intend to query your "other" feature service with passed in a parameter when opening the form. The JS script fires upon opening .
... View more
02-09-2019
07:13 AM
|
0
|
0
|
4000
|
POST
|
I can answer #2 - it can be used with any rest service. You just need a mechanism to feed a value into a field in your survey, which the JS script takes to query "the other" feature service. In my case I passed Workforces' location into FacilityID. I then took the value of FacilityID (now populated) and used that in my JS query to "the other" feature service. I can't answer #1 - I'd ask James Tedrick
... View more
02-08-2019
03:17 PM
|
0
|
2
|
4000
|
POST
|
sadly that won't work - it runs without error, but fails to select results.
... View more
02-08-2019
01:25 PM
|
0
|
0
|
621
|
POST
|
Joshua Bixby Thanks! How would I modify this to be within the past hour? I used the below: CreationDate BETWEEN CURRENT_TIMESTAMP - 0.0416666666666667 AND CURRENT_TIMESTAMP It appears to work but there must be something more elegant...
... View more
02-08-2019
01:01 PM
|
0
|
1
|
621
|
POST
|
Hello ArcGIS Pro team, Within Pro I am able to pull in hosted feature services which are related. I am then able to configure the popups within Pro to show me attribute values from these related tables. For example: Related Table 1: {R0L0Small_Valve_AuditsL2Small_Valve_Audit_Results\TURNS:MAX} Related Table 2: {R1L0Small_Valve_AuditsL1Small_Valve_Audit_Candidates\TURNS:MAX} I therefore thought it might be possible to also do a field calculation leveraging values from these same related tables. For example: TURNS = !R0L0Small_Valve_AuditsL2Small_Valve_Audit_Results\TURNS! However, this seems a step too far as I'm getting 000539: Error message from Python . Is this possible at all or is this a lost cause?
... View more
02-08-2019
08:23 AM
|
2
|
0
|
1136
|
POST
|
02-08-2019
07:59 AM
|
0
|
1
|
621
|
POST
|
Is it possible to use the #select layer by attribute in #arcgis pro 2.3 to select records created today? I'm trying CreationDate = timestamp NOW() But getting an error.
... View more
02-08-2019
07:20 AM
|
0
|
3
|
1901
|
POST
|
Is it possible to use the select layer by attribute to select records created today? I'm trying CreationDate = timestamp NOW() But getting an error.
... View more
02-08-2019
07:16 AM
|
0
|
0
|
705
|
POST
|
I figured this out immediately after posting my original question. I think the value for !assignedDate! isn't actually saved back to the feature service before the task attempts to run the next calculate of !assignedDate!+datetime.timedelta(days=14) Instead I simply calc !assignedDate! using datetime.datetime.now() and !dueDate! using datetime.datetime.now()+datetime.timedelta(days=14)
... View more
02-07-2019
06:10 PM
|
0
|
0
|
416
|
POST
|
Hello ArcGIS Pro team & ArcGIS Pro Tasks team I'm using the additional actions steps to calculated fields when exiting a step. I followed this documentation to Calculate the current date into my assignedDate field using: time.strftime("%m/%d/%Y") I then attempt to add 14 days to the current date and calculate that value into my dueDate field. According to the same page I should be able to use: !assignedDate!+datetime.timedelta(days=14) If i perform the field calculation manually this works fine. However, when using the exact same expression in my additional actions I get the below error
... View more
02-07-2019
05:06 PM
|
0
|
1
|
496
|
POST
|
Hello again Christine Leslie Jason CameranoAmir Bar-Maor Charles FernandesArcGIS Pro Tasks and ArcGIS Pro teams. I adjusted my task to try to get something working. It's now configured as shown in the below. Now I: Select features from Featureclass A Perform an append from Featureclass A to B and ask the additional actions to create a selection set of these new features appended into B, which I name NEWAPPENDEDFEATURES. I set the additional actions of the follow on step to start by selecting the features in NEWAPPENDEDFEATURES so the field calculation I use to set some Workforce for ArcGIS values will only apply to these features. However, as you'll see in the below when I run the task the append occurs, but the selection of features within NEWAPPENDEDFEATURES fails to occur, meaning ALL features inside of Featureclass B get field calculated with the Workforce for ArcGIS values. Again, any help is appreciated.
... View more
02-01-2019
07:37 AM
|
0
|
2
|
1599
|
POST
|
Hello Christine Leslie, Jason Camerano, Amir Bar-Maor,ArcGIS Pro Tasks team and ArcGIS Pro team. I am attempting to use the "Additional Actions" capability of Tasks to both copy attributes and calculate fields either side of an Append function. However, neither are performing as expected. Here are the steps within my task: Select several points in Featureclass A, to be Appended into Featureclass B Append the selected points from A to B. Within the Append parameters I set: Input Layer to Featureclass A (including a selection set of features within this Featureclass) Target Dataset to Featureclass B {location} field of Target to get fieldmapped with {VALVE_NO} of Input (this is a unique ID field) 2a. Additional Action when exiting the step to Calculate Field values into only the Features or records created in this step - ie: only those points just appended to this layer in this step. Although the Append from step 2 works, the field mapping to pass {VALVE_NO} into {location} fails to occur. Further, the Additional Action supposed to occur at the end of the step to field calculate values into the fields of the features just appended also fails and gives me the below error: Please can someone point out where I'm going wrong? Thanks
... View more
01-31-2019
05:32 AM
|
0
|
9
|
1856
|
POST
|
Dan Patterson - yes, status exists and is a numeric field
... View more
01-29-2019
10:29 AM
|
0
|
1
|
855
|
POST
|
Hi Dan Patterson I'm having a very similar issue when attempting to run a field calculation on features appended using a Pro Task. The append works fine, but I ask the Task to also calculate three values on those newly appended "Features or records created in this step" . These field calc's fail to occur. Screenshots of my setup are below:
... View more
01-29-2019
09:50 AM
|
0
|
3
|
855
|
Title | Kudos | Posted |
---|---|---|
1 | 12-07-2018 08:23 AM | |
1 | 04-06-2018 08:25 AM | |
1 | 01-10-2019 03:17 PM | |
1 | 01-04-2019 08:09 AM | |
2 | 02-08-2019 08:23 AM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:24 AM
|