Latest Contributions by VinceE

Hey @DrewFlater, a follow up to this. I just tried to use arcpy's AddField with a "BIGINTEGER" data type, and ran into a similar issue as above: ERROR 000800: The value is not a member of TEXT | FLOAT | DOUBLE | SHORT | LONG | DATE | BLOB | RASTER | GUID. Failed to execute (AddField). I'm not going to open a Pro Idea because... this issue of new data types clearly hasn't been addressed in a lot of places, so the "idea" would extremely general. I'll leave the prioritization decisions to you all. Thanks again for the initial reply. ... View more

Fair enough, I appreciate the insights. I'll go ahead and play around with replacing the string in FeatureSetByName. Thanks again! ... View more

Thanks for the inputs @RPGIS, but the code I have provided already "works"--even without specifying this line below. Maybe that's because the Arcade "environment" knows that all feature classes/tables will have an ObjectID, so you don't need to specify? Regardless, it seems inconsistent. But I don't have it listed in my version, and things work as expected. var OID = $feature.OBJECTID My issue is that I don't want to have to specify the field name three different times in the same code. I'm not saying Python is without problems, but coming from Python there would never be a case where I would have to hard-code a string three different times in the same extremely small block of code. I would assign the string field name to a variable, and then use that variable in every instance where it is needed--if the field name changes, I change the single instance of that variable assignment, and it updates everywhere. In my example, and both of your examples, we are specifying the same field name "Name_Text" three different times in the same tiny script. If this is a bug, fine, but if this is how the language was designed... why? ... View more

Appreciate the information Drew, thank you. ... View more

Well at least the problem is repeatable. Thanks for testing. ... View more

Appreciate the input, thanks! This option will have to do for now. Here's what my implementation looks like: HHMM is a TEXT field that the user types in, HH is a FLOAT field that gets calculated. Figured reading HH would be more intuitive to understand than MM, but the concept is the same. I try to use the same "template" for Attribute Rules, so this is probably overly verbose, but here's the automatic calculation from HH:MM text to HH float:   /* Converts a text HH:MM format field and converts it to a float HH field. */ //---------------------------------------------------------------------// // FUNCTIONS function calculateHH(hhmm) { // Set up results dict. If all checks pass, return this as-is. var result = Dictionary("VALUE", null, "ERROR", null) if (IsEmpty(hhmm)) { return result } Console(hhmm) var timeArr = Split(hhmm, ":") var hh = Number(timeArr[0]) + (Number(timeArr[1]) / 60) Console(`${hhmm} --> ${hh}`) result["VALUE"] = Round(hh, 2) return result } //---------------------------------------------------------------------// // INPUTS var hhmm = $feature.Hiking_HHMM //---------------------------------------------------------------------// // MAIN var fldUpdates = Dictionary() // Convert HHMM text to MM float ---------------- var result = calculateHH(hhmm) if (!IsEmpty(result["ERROR"])) {return {"errorMessage": `ERROR: ${result}`}} else {fldUpdates["Hiking_HH"] = result["VALUE"]} Console({"result": {"attributes": fldUpdates}}) return {"result": {"attributes": fldUpdates}}     And my solution to verifying the initial HH:MM inputs:   /* Script provides validation for a TEXT field that should contain a time duration in the format H?H?:MM. There are several checks, since RegEx is not available. 1) Blank strings are not allowed; null values are fine 2) Format must contain a colon--as in 3:30, 12:04, :37 3) Values on either side of the colon must be numeric 4) Hours are optional, but must be 0 - 23 5) Minutes must always be two characters, and numeric values 0 - 59 This script is meant to be used as Calculation type AR, rather than a Constaint AR. */ //---------------------------------------------------------------------// // FUNCTIONS function timeValidate (time) { // Set up results dict. If all checks pass, return this as-is. var result = Dictionary("VALUE", time, "ERROR", null) // First check empty, then null. Can't do both simultaneously nicely. if ((TypeOf(time) == "String") && Trim(time) == "") { result["ERROR"] = "Blank input is not allowed." return result } else if (IsEmpty(time)) { return result } // Console(timeArray, Count(timeArray)); // Must contain one ":", yields two elements with Split(). if (Count(timeArray) != 2) { result["ERROR"] = "Format must contain one colon." return result } // Check if both values in the array are numbers. for (var i in timeArray) { var tPart = timeArray[i] Console(`PART: ${i}, VAL: ${tPart}, ASNUM: ${Number(tPart)}, ISNAN: ${IsNan(Number(tPart))}`) // If Number returns NaN, "Casting a non-numeric text or undefined to a number". if (IsNan(Number(tPart))) { result["ERROR"] = "At least one value is not numeric." return result } // Hours validation, the first array item. if (i == 0) { Console(`VALIDATING HOURS: ${tPart}`) // Comparison operators coerce Text to Number for comparison. if (tPart > 23 || tPart < 0) { result["ERROR"] = "Hours must be 0-23." return result } } // Minutes validation, the second array item. else if (i == 1) { Console(`VALIDATING MINUTES: ${tPart}`) if (Count(tPart) != 2) { result["ERROR"] = "Minutes must be two digits." return result } else if (tPart > 59 || tPart < 0) { result["ERROR"] = "Minutes must be 0-59." return result } } } return result } //---------------------------------------------------------------------// // INPUTS // Expects($feature, "Shape_Length", "MPH", "Miles") var time = $feature.Hiking_HHMM // DERIVED var timeArray = Split(time, ":") Console(`TIME ARR: ${timeArray}`) //---------------------------------------------------------------------// // MAIN var fldUpdates = Dictionary() // result = {"VALUE": time, "ERROR": error string OR null} var result = timeValidate(time) // If an error is returned in results dict, show and make no changes. if (!IsEmpty(result["ERROR"])) {return {"errorMessage": `ERROR: ${result} Please use H?H?:MM format.`}} // Else, add the field update information to the running updates log. else {fldUpdates["Hiking_HHMM"] = time} Console({"result": {"attributes": fldUpdates}}) return {"result": {"attributes": fldUpdates}}     ... View more

For "data" reasons, a great solution--at the resolution I require, even minutes would work. My issue is that if a user is transcribing a record from elsewhere, say "7:37", they have to do the math to convert those hours into minutes (or hours and minutes into seconds, if seconds are my unit). Not a huge deal, but an extra step, and possibly error-prone. The other thing is quickly reading the table. I want to be able to read these records at a glance. Number of seconds (beyond a minute or two) means virtually nothing to me, and even minutes can get difficult: 407 minutes takes me a little while to process. So I'd really want that to show as HH:MM. And I don't know of a table "display" setting that would allow the math required to calculate that from seconds/minutes alone, and an Attribute Rule would... change the actual underlying data value? Plus, an Attribute Rule returning a value with the colon would be problematic with a DOUBLE field type. Storing as minutes is probably going to be the only solution here, but it's annoying that it can't be displayed in an easily readable way. My best bet might be to use an Attribute Rule to calculate the minutes into a SHORT/DOUBLE field from a TEXT field. So the user can type in 5:49 or whatever in the TEXT field, and then an Attribute Rule calculates the raw number of minutes into a different numeric field, and then valid sorting can take place on the MINUTES field. Appreciate the comment, thanks! ... View more