Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Cancel
- Home
- :
- About FranklinAlexander
FranklinAlexand
Frequent Contributor
since
05-04-2016
11-06-2025
246
Posts created
4
Kudos given
25
Solutions
48
Kudos received
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
My Ideas
(1 Idea Submissions)Latest Contributions by FranklinAlexander
|
POST
|
I didn't have that option turned on and it zooms to my location now, but I still have an issue, however, with no results being displayed in the dropdown menu. I should be seeing an address instead of just coordinates, so something is still amiss.
... View more
03-13-2024
11:34 AM
|
0
|
0
|
2146
|
|
POST
|
I have created an Experience Builder Developer application and configured a Search widget with the Use current location option enabled. It does basically the same thing as the Locate tool in the map and if you have an Action configured can zoom to your location on the map. It can also be used with other widgets such as the Near Me widget by allowing users to automatically search for features a given distance from their location without having to type an address. The problem I am having is that when a user clicks the Use current location button the first time nothing happens. As you can see, the input element is populated with a set of coordinates, but no address shows up in the dropdown menu and there is no zoom action. If I clear the input and try again, it works as expected. As an aside, Experience Builder online has a similar issue, except that the menu populates on the first click, but only with coordinates, and once again there is no zoom action. I have already reported the this to Esri support as a bug, but was wandering if any one besides me has experienced the same issue. I am using EXB version 1.13.
... View more
03-13-2024
11:12 AM
|
0
|
4
|
2201
|
|
POST
|
I am trying to create an attribute rule that populates a field in an origin table when a field in a child table is updated. This could be from adding a new record, or updating an existing record. Both tables have a field named "NID", which is being used as the relationships primary and foreign keys. The NID field in the parent table has unique values and the NID field in the child table can have multiple of the same value, so the relationship is many to 1. The problem I am running into is when I try and return the results. I have looked at examples and read the Esri documentation, but still find if very confusing. I keep getting an error about Global IDs and not sure why. Both of the tables have GobalIDs, but they are not being used as key fields so I don't understand the error. Here is my code so far: var parTble = FeatureSetByName($datastore, "ParentTable", ["NID"], false)
var spTble = FeatureSetByName($datastore, "Species_table", ["NID"], false)
var nid = $feature.NID
//var nid = 4
Console("NID = " + Text(nid))
var nidCnt = Count(Filter(spTble, "NID = @nid"))
Console("Count = " + Text(nidCnt))
var relatedRecord = FeatureSetByRelationshipName($feature, "ParentTable_Species_table", ["Species_table"])
Console("Parent table feature count = " + Text(Count(relatedRecord)))
if(Count(relatedRecord) == 0) {
Console("Adding new record to parent table")
return null
}
return {
//"result": Text(nidCnt) + " records found for NID #" + Text(nid),
"edit": [{
"className": "ParentTable",
"updates": [{
"NID": "NID",
"attributes": {relatedRecord: Number(nidCnt)}
}]
}]
} Also, I know I need to add a new record to the Parent table if a new NID is entered in the child table (ex 7), but I will worry about that when I get this working! 🙂
... View more
02-16-2024
07:09 AM
|
0
|
0
|
3223
|
|
POST
|
@IanRatcliffe Yes, that is the exact issue I was having, but only occurring when I tried to run my script from a script tool. I could run it from the Python IDLE without issue. Apparently, at least from my experience dealing with this, for some reason, the Table Export conversion tool field mappings could not see my file path to the input layer whenever I used a variable for the path. It doesn't make sense because I used the same variable in other geoprocessing tools and they ran just fine. Just some quirky behavior with this tool. I was able to get it working by setting my workspace environment to the gdb that contained the input layer for the field map. This works: outPath = arcpy.GetParameterAsText(0)
TempDB_name = "Temp.gdb"
TempWS = os.path.join(outPath, TempDB_name)
with arcpy.EnvManager(scratchWorkspace=TempWS, workspace=TempWS): # setting the env made the difference
excelToTable = "excelToTable" # This is my input table
fm = ("list_name \"List Name\" true true false 100 Text 0 0,First,#,excelToTable,list_name,0,254;" +
"item_id \"Item ID\" true true false 10 Text 0 0,First,#,excelToTable,item_id,0,254;" +
"itemname \"Item Name\" true true false 100 Text 0 0,First,#,excelToTable,itemname,0,254;" +
"material \"Material\" true true false 50 Text 0 0,First,#,excelToTable,material,0,254;" +
"quantity \"Quantity\" true true false 255 Long 0 0,First,#,excelToTable,quantity,0,254;" +
"description \"Description\" true true false 255 Text 0 0,First,#,excelToTable,description,0,254;" +
"latitude \"Latitude\" true true false 8 Double 14 16,First,#,excelToTable,latitude,0,254;" +
"longitude \"Longitude\" true true false 8 Double 14 16,First,#,excelToTable,longitude,0,254;" +
"altitude \"Altitude\" true true false 255 Float 0 0,First,#,excelToTable,altitude,0,254;" +
"radius \"Radius\" true true false 255 Float 0 0,First,#,excelToTable,radius,0,254;" +
"location \"Location\" true true false 100 Text 0 0,First,#,excelToTable,location,0,254;" +
"timestamp \"Timestamp\" true true false 20 Text 0 0,First,#,excelToTable,timestamp,0,254;" +
"dt \"Datetime\" true true false 255 Date 0 0,First,#,excelToTable,dt,0,254;" +
"project_name \"Project Name\" true true false 50 Text 0 0,First,#,excelToTable,project_name,0,254")
MDD_exportTable = "MDD_exportTable"
arcpy.conversion.ExportTable(in_table=excelToTable, out_table=MDD_exportTable, field_mapping=fm)
... View more
02-15-2024
08:46 AM
|
0
|
0
|
5254
|
|
POST
|
I was wrong about wrapping the fields, that is not the issue. The problem occurs when I use a variable in place of the hard file path for the input table. This is a huge problem, because the path comes from a parameter and must variable. Otherwise it defeats the whole purpose of the script tool, which is the portability! This: "longitude \"Longitude\" true true false 255 Text 0 0,First,#,C:\\GIS_projects\\...\\...\\...\\Temp.gdb\\excelToTable,longitude,0,254; Needs to be this: "longitude \"Longitude\" true true false 255 Text 0 0,First,#,excelToTable,longitude,0,254; If I print the variable excelToTable to the processing details window, they are exactly the same. Any ideas about how I can address this?
... View more
02-14-2024
11:01 AM
|
2
|
3
|
5315
|
|
POST
|
The issue only exists for me when I try and execute a script from a script tool. I have been able to run the Export Table conversion tool successfully in model builder, Arc Pro, and from the Python IDLE. After further investigation, it appears that if I leave the field mapping in one continuous line and don't wrap each field to the next line like I did in my code sample, it works as expected and my fields are updated to the new types. I don't understand why this is only an issue when I execute my script from a script tool, when I can execute the exact same script from the IDLE and it works just fine. I just find the long continuous never ending line of code to be a little annoying because it's messy and I have to scroll, scroll, and scroll some more to see all of the mapping parameters!! It also makes the parameters difficult to edit if needed. To Robert, Yes, I did get that update a couple of days ago, but OIT would have to uninstall it. I will just wait for the next update and see if it makes any difference.
... View more
02-14-2024
10:26 AM
|
1
|
4
|
5321
|
|
POST
|
I have done this hundreds of times, but something seems to have changed in the last Arc Pro update. I have a Python script where I am trying to convert a spreadsheet into a point layer. Below is what I tried first, but the latitude and longitude fields will not convert to Double. # Process: Excel To Table (Excel To Table) (conversion)
arcpy.AddMessage("Converting spreadsheet to DB Table")
logging.info("Converting spreadsheet to DB Table")
excelToTable = os.path.join(TempWS, "excelToTable")
arcpy.AddMessage("Excel to table path " + excelToTable)
arcpy.conversion.ExcelToTable(Input_Excel_File=spreadsheet, Output_Table=excelToTable, Sheet="Debris Harvest Data Florida")
fm = ("list_name \"List Name\" true true false 100 Text 0 0,First,#,excelToTable,list_name,0,254;" +
"item_id \"Item ID\" true true false 10 Text 0 0,First,#,excelToTable,item_id,0,254;" +
"itemname \"Item Name\" true true false 255 Text 0 0,First,#,excelToTable,itemname,0,254;" +
"material \"Material\" true true false 255 Text 0 0,First,#,excelToTable,material,0,254;" +
"quantity \"Quantity\" true true false 255 Text 0 0,First,#,excelToTable,quantity,0,254;" +
"description \"Description\" true true false 255 Text 0 0,First,#,excelToTable,description,0,254;" +
"latitude \"Latitude\" true true false 8 Double 0 0,First,#,excelToTable,latitude,0,254;" +
"longitude \"Longitude\" true true false 8 Double 0 0,First,#,excelToTable,longitude,0,254;" +
"altitude \"Altitude\" true true false 255 Float 0 0,First,#,excelToTable,altitude,0,254;" +
"radius \"Radius\" true true false 255 Float 0 0,First,#,excelToTable,radius,0,254;" +
"location \"Location\" true true false 255 Text 0 0,First,#,excelToTable,location,0,254;" +
"timestamp \"Timestamp\" true true false 255 Text 0 0,First,#,excelToTable,timestamp,0,254;" +
"dt \"Datetime\" true true false 255 Date 0 0,First,#,excelToTable,dt,0,254;" +
"project_name \"Project Name\" true true false 255 Text 0 0,First,#,excelToTable,project_name,0,254;" +
"project_id \"Project ID\" true true false 255 Long 0 0,First,#,excelToTable,project_id,0,254;" +
"username \"Username\" true true false 255 Text 0 0,First,#,excelToTable,username,0,254;" +
"user_index \"User Index\" true true false 255 Long 0 0,First,#,excelToTable,user_index,0,254;" +
"manual_upload \"Manual Upload\" true true false 255 Text 0 0,First,#,excelToTable,manual_upload,0,254;" +
"event_name \"Event Name\" true true false 255 Text 0 0,First,#,excelToTable,event_name,0,254;" +
"id \"ID\" true true false 255 Text 0 0,First,#,excelToTable,id,0,254;" +
"log_index \"Log Index\" true true false 255 Long 0 0,First,#,excelToTable,log_index,0,254")
# Process: Export Table (Export Table) (conversion)
arcpy.AddMessage("Exporting table and mapping fields")
logging.info("Exporting table and mapping fields")
MDD_exportTable = os.path.join(TempWS, "MDD_exportTable")
arcpy.conversion.ExportTable(in_table=excelToTable, out_table=MDD_exportTable, field_mapping=fieldMap)
# Process: XY Table To Point (XY Table To Point) (management)
arcpy.AddMessage("Displaying XY values and creating point feature class")
logging.info("Displaying XY values and creating point feature class")
MDD_tableToPoint = os.path.join(TempWS, "MDD_tableToPoint")
arcpy.management.XYTableToPoint(in_table=MDD_exportTable, out_feature_class=MDD_tableToPoint, x_field="lon", y_field="lat",
coordinate_system="GEOGCS[\"GCS_WGS_1984\",DATUM[\"D_WGS_1984\",SPHEROID[\"WGS_1984\",6378137.0,298.257223563]],PRIMEM[\"Greenwich\",0.0],UNIT[\"Degree\",0.0174532925199433]];-400 -400 1000000000;-100000 10000;-100000 10000;8.98315284119521E-09;0.001;0.001;IsHighPrecision") In the exported table, the latitude and longitude fields are still Text fields and I cannot display XY values using these fields. I also tried adding new fields in the field map and then calculating them, but iy seems as though the Table Export tool is ignoring the field mapping altogether because there are no new fields created to run the Calculate Field tool on. I noticed that in the last ArcPro update, the field mapping tool interface has changed, so I am wandering if something got messed up in the last update. I really don't want to have to write an extra 100 lines of code to do this, so if anyone has any insight please share. 🙂
... View more
02-14-2024
08:36 AM
|
3
|
12
|
6353
|
|
POST
|
I have a custom Filter widget that was created by another developer and I noticed that on subsequent Filtering tasks, the results didn't make sense. After looking at the code, I think I found the issue, but I don't know how to fix it. From what I can tell the updateQueryParams function isn't working the way I would expect. Instead of overwriting the where clause when called, it seems to be appending the new where clause to the previously loaded where clause. Does any one know if this is the way this function should work? I need to be able to clear the previous clause completely before updating the params, but I am not familiar enough with the 4X api yet. Here is the code: const executeAttributeQuery = async (props) => {
let wc = "";
if (filterItems.length > 0) {
setMessage("")
for (var i = 0; i < filterItems.length; i++) {
if (i == 0) wc += filterItems[i].filter;
else wc += " AND " + filterItems[i].filter;
}
} else {
wc = "1=1";
setMessage('No items to filter')
}
console.log("Before On 345 ");
console.log("where ", wc)
const ds0 = getFeatureLayerDataSource(props.useDataSources[0].dataSourceId);
const ds1 = getFeatureLayerDataSource(props.useDataSources[1].dataSourceId);
const ds2 = getFeatureLayerDataSource(props.useDataSources[2].dataSourceId);
ds0.updateQueryParams(null, props.id); //This seems to be the only
ds1.updateQueryParams(null, props.id); //way to clear the previous
ds2.updateQueryParams(null, props.id); //where clause, but it's not
//optimal
const queryParams: FeatureLayerQueryParams = {
outFields: ["OBJECTID"],
where: wc,
returnGeometry: false,
};
const records0 = await ds0.query(queryParams);
let wc1 = getWcSpatial(records0.records) //returns array of object IDs
console.log("query params ", queryParams) //where clause is correct here.
if (wc1.length > 0) {
const qp1: SqlQueryParams = { where: wc1 }
console.log("attrubute query params ", qp1)
ds0.updateQueryParams(qp1, props.id); //does not update, appends to
//previously loaded where clause.
ds1.updateQueryParams(qp1, props.id);
ds2.updateQueryParams(qp1, props.id);
publishDataFilterAction(props.id, props.useDataSources[0].dataSourceId);
} else {
setMessage("No matches.")
const qp1: SqlQueryParams = { where: "1=1" };
console.log("attrubute query params no match ", qp1)
ds0.updateQueryParams(qp1, props.id);
ds1.updateQueryParams(qp1, props.id);
ds2.updateQueryParams(qp1, props.id);
publishDataFilterAction(props.id, props.useDataSources[0].dataSourceId);
}
} The above code is the source code from the widget.tsx file, but the app has already been exported to the server so any changes I make must be in the compiled code which is not ideal. where clause from 1st query: Horseback riding = 'y' where clause from subsequent query: Horseback riding = 'y' and Bicycling = 'y' The reason I don't want to run the updateQueryParams function to clear out the where clause is because as soon as it runs, all of the features display on the map briefly until the Filter executes.
... View more
01-17-2024
12:15 PM
|
0
|
0
|
631
|
|
POST
|
I am trying to create custom content for a popup and I need to wrap text around an image. To do this, I am trying to add a 'float' property to the image style, but it is apparently being removed when I close the Arcade editor. I know my syntax is correct and it is not a typo, so is this just something that Esri does not allow? Here is my code: <p style='font-size:1.15em'><b>Species Name</b></p>
<div>
<img src='<img url>' style='width:40%; margin-right:20px; float:left;'>
<p>Descriptive sentence</p>
</div> The other style properties are working so this is very frustrating. As you can see from the images below, the float property is not being applied. This is how it should look after applying the float property in the console: Can someone please let me know what I am missing?
... View more
01-05-2024
08:07 AM
|
0
|
0
|
601
|
|
POST
|
I have a List Widget that is using a table as it's source data, but the table has 1286 records. Since there is no filter applied when the application loads, the List Widget shows all 1286 records, most of which are repetitive since there are only 33 unique values in my selected field. I would like to either show a pre-filter subset of the data, or just a message ("Please select a county to see fish species"). I did try the 'View for empty selection' option for the source table, but it isn't working. I clicked the gear icon and filtered the data by county as in the image, but the List still wants to fill with all of the records instead of the filtered records (18 in total). The app has been created using Experience Builder Developer v1.12 and you can find a downloaded version here: https://gis.myfwc.com/InDevelopment/Alexander/FishRangeFinder/FishRangeFinder_dev6/
... View more
11-02-2023
06:28 AM
|
0
|
1
|
837
|
|
POST
|
Does any one know of a way for the Esri popup content to show initially on a mobile device? When clicking a feature in desktop layout, the popup displays and initially shows the content. If you want to hide the content, you must click the caret icon in the top right of the popup. In mobile layout, the content is hidden initially and the caret icon must be click to show the content. This is not optimal to me and I would like the content to show initially on a mobile device like it does on the desktop. You would think there would be a setting some place to allow for "expanding" the content panel on load, but I haven't been able to find one.
... View more
10-30-2023
12:57 PM
|
0
|
2
|
983
|
|
POST
|
Ha! Yes, it's amazing often that seems to work. In this case, I tried that an then some but after a close examination of the Chrome console I finally found the culprit. The max-height property in my custom theme style.css file was set to 400px for the popup dialog so I just removed the property and that fixed the issue. Not sure if I did that or if it was an inherited property, but my popups look a lot better.
... View more
10-27-2023
07:52 AM
|
0
|
0
|
1960
|
|
POST
|
Nothing that I can see: I tried clicking in the space beneath the html to make sure the was no extra space and there wasn't. The cursor always remains in the expression. Also, if there was any extra space I would think it would show up in the Web Map.
... View more
10-26-2023
09:11 AM
|
0
|
2
|
2020
|
|
POST
|
I am trying to add some custom some very simple content to a popup in a Web Map. The popup displays fine in the Web Map, but when I open the popup from an Experience Builder app, there is a HUGE space below the text. The seems like a serious bug to me, but has any one else had this issue? I am using EXB developer 1.12. Please refer to images: HUGE empty space!
... View more
10-26-2023
08:47 AM
|
0
|
6
|
2038
|
|
POST
|
Just a quick follow up, but I have confirmed it's not a script issue because the Delete tool doesn't run from ArcPro on the dataset either. My DB Administrator mentioned that is seems the issue was first documented after the ArcPro 3.0 update which makes me think it is a bug. I don't think this is a 'Editing' issue at all (hence the error shouldn't be taken at face value), but probably more of an 'access' problem. I will post if we find a solution, but would be interested if any one else has encountered a similar issue.
... View more
10-02-2023
05:10 AM
|
0
|
1
|
1656
|
My kudoed posts
| Title | Kudos | Posted |
|---|---|---|
| 8 | 10-28-2025 10:15 AM | |
| 2 | 10-14-2025 06:36 AM | |
| 1 | 09-16-2022 09:31 AM | |
| 1 | 06-13-2024 05:45 AM | |
| 1 | 06-26-2025 06:28 AM |
Activity Feed
- Got a Kudo for A little disappointed with the latest Near Me widget update as it pertains to the use current location functionality. 3 weeks ago
- Got a Kudo for A little disappointed with the latest Near Me widget update as it pertains to the use current location functionality. 4 weeks ago
- Got a Kudo for A little disappointed with the latest Near Me widget update as it pertains to the use current location functionality. 11-06-2025 06:50 AM
- Got a Kudo for A little disappointed with the latest Near Me widget update as it pertains to the use current location functionality. 10-29-2025 08:55 AM
- Got a Kudo for A little disappointed with the latest Near Me widget update as it pertains to the use current location functionality. 10-29-2025 06:26 AM
- Got a Kudo for A little disappointed with the latest Near Me widget update as it pertains to the use current location functionality. 10-29-2025 06:17 AM
- Got a Kudo for A little disappointed with the latest Near Me widget update as it pertains to the use current location functionality. 10-29-2025 03:04 AM
- Got a Kudo for A little disappointed with the latest Near Me widget update as it pertains to the use current location functionality. 10-28-2025 11:34 AM
- Posted Re: What is new in Near Me (October 2025 ArcGIS Online update) on ArcGIS Experience Builder Blog. 10-28-2025 10:29 AM
- Posted A little disappointed with the latest Near Me widget update as it pertains to the use current location functionality on ArcGIS Experience Builder Ideas. 10-28-2025 10:15 AM
- Got a Kudo for Re: Unable to enable editing for a field in Map Viewer. 10-22-2025 09:32 AM
- Got a Kudo for Re: Unable to enable editing for a field in Map Viewer. 10-14-2025 08:30 AM
- Posted Re: Unable to enable editing for a field in Map Viewer on ArcGIS Online Questions. 10-14-2025 06:36 AM
- Posted Re: Unable to enable editing for a field in Map Viewer on ArcGIS Online Questions. 10-13-2025 12:03 PM
- Posted Re: Sidebar collapse button text and/or flash on ArcGIS Experience Builder Ideas. 10-10-2025 06:51 AM
- Kudoed Sidebar collapse button text and/or flash for Jamie_Leitch_CNF. 10-10-2025 06:44 AM
- Posted Unable to enable editing for a field in Map Viewer on ArcGIS Online Questions. 10-10-2025 05:46 AM
- Tagged Unable to enable editing for a field in Map Viewer on ArcGIS Online Questions. 10-10-2025 05:46 AM
- Tagged Unable to enable editing for a field in Map Viewer on ArcGIS Online Questions. 10-10-2025 05:46 AM
- Got a Kudo for Query widget menu will not populate. 10-01-2025 11:30 AM
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
11-06-2025
04:20 AM
|