|
POST
|
See these settings in the App setting section of the Field Map Designer Set map behavior when collecting new features Determine whether manual location can be used for feature collection
... View more
09-04-2025
05:12 AM
|
0
|
8
|
1524
|
|
POST
|
That error is usually associated with a problem in the Filter function sql statement. Check your fields and if those field names and values are valid. You can make the sql statement easier to read using variable substitution (see the documentation). You don't have to worry about quotes using this syntax var student = f["nbid2"];
var sdate = ToUTC(f["Max_Date"]);
var sdate_local = f["Max_Date"];
var sql = "nextrecheckdate = @sdate AND nbid2 = @student";
... View more
08-27-2025
08:39 AM
|
4
|
1
|
877
|
|
POST
|
Glad to point you in the right direction! Don't forget to click the "Accept as Solution" button
... View more
08-26-2025
12:07 PM
|
0
|
0
|
423
|
|
POST
|
Glad to point you in the right direction! Don't forget to click the "Accept as Solution" button
... View more
08-26-2025
12:06 PM
|
0
|
0
|
593
|
|
POST
|
This technical support document explains how you can report issues with the Geocoder, basemaps, or routing services.
... View more
08-26-2025
07:16 AM
|
1
|
2
|
675
|
|
POST
|
This technical support document explains how you can report issues with the Geocoder, basemaps, or routing services.
... View more
08-26-2025
06:23 AM
|
0
|
2
|
478
|
|
POST
|
This appears to be working in Developer Edition v1.18
... View more
08-25-2025
01:34 PM
|
1
|
0
|
469
|
|
DOC
|
@AlexWolf1 You can do that by clicking the "Interact with a Map widget" option (1), clicking on the map under "Specify which layers will be displayed for each map" (2), turn on "Customize layers" (3), and uncheck the layers you don't want to show (4)
... View more
08-21-2025
11:57 AM
|
0
|
0
|
6886
|
|
POST
|
After giving this a little thought, there's an even faster way to do this. Cycling through each set of lines in each service area polygon to write them to a dictionary is pretty inefficient. Instead, this version unions each of the service areas into a single polygon to use in a single Intersects function. And if there is only one polygon in the service area, it skips that step. //Define the Enterprise portal connection
var myportal = Portal("https://samplesite.net/portal");
// Get the line layer: UN - Sewer Lines
var SewerLines = FeatureSetByPortalItem(
myportal,
"2c08361d8abe4308afba3d25c857a11c",
3,
["*"],
true
);
// Get the polygon layer: Separated Service Areas,
//filtered for Core Service Area feature only
var CoreSvcAreas = Filter(
FeatureSetByPortalItem(
myportal,
"41c17045b4cf4359a8237db163fe82a6",
0,
["*"],
true
),
"ServiceAreaName = 'RVSS Core Service Area'"
);
// return the intersection if there's only one service area
if (Count(CoreSvcAreas) == 1) return Intersects(SewerLines, First(CoreSvcAreas));
// otherwise, union the service areas together and return the intersection
var areas = [];
for (var area in CoreSvcAreas) {
Push(areas, area)
}
return Intersects(SewerLines, Union(areas));
... View more
08-21-2025
11:37 AM
|
1
|
0
|
1398
|
|
POST
|
I had edited my first response to explain why you were getting that error. In addition, there was another issue with your code. A data expression has to return a FeatureSet, but you were returning an array. You would have to convert the array of lines into a FeatureSet to use it in the dashboard. This code should work when a service area is comprised of multiple polygons //Define the Enterprise portal connection
var myportal = Portal("https://samplesite.net/portal");
// Get the line layer: UN - Sewer Lines
var SewerLines = FeatureSetByPortalItem(
myportal,
"2c08361d8abe4308afba3d25c857a11c",
3,
["*"],
true
);
// Get the polygon layer: Separated Service Areas,
//filtered for Core Service Area feature only
var CoreSvcAreas = Filter(
FeatureSetByPortalItem(
myportal,
"41c17045b4cf4359a8237db163fe82a6",
0,
["*"],
true
),
"ServiceAreaName = 'RVSS Core Service Area'"
);
var dict = {
fields: Schema(SewerLines)["fields"],
geometryType: Schema(SewerLines)["geometryType"],
features: []
};
for (var CoreSvcArea in CoreSvcAreas) {
for (var line in Intersects(SewerLines, CoreSvcArea)) {
var attributes = {};
for (var attr in line) {
attributes[attr] = line[attr];
}
Push(dict["features"], { attributes: attributes });
}
}
return FeatureSet(dict);
... View more
08-21-2025
10:27 AM
|
0
|
2
|
1415
|
|
POST
|
Is each of the CoreSvcAreas a single polygon or is it multiple polygons? If it's a single polygon, then you can make this much simpler //Define the Enterprise portal connection
var myportal = Portal("https://samplesite.net/portal");
// Get the line layer: UN - Sewer Lines
var SewerLines = FeatureSetByPortalItem(
myportal,
"2c08361d8abe4308afba3d25c857a11c",
3,
["*"],
true
);
// Get the polygon layer: Separated Service Areas,
// filtered for Core Service Area feature only
// This works only if there is one polygon per service area
var CoreSvcArea = First(
Filter(
FeatureSetByPortalItem(
myportal,
"41c17045b4cf4359a8237db163fe82a6",
0,
["*"],
true
),
"ServiceAreaName = 'RVSS Core Service Area'"
)
);
return Intersects(SewerLines, CoreSvcArea); You were getting that error in the Filter function since you had a syntax wrong. Filter expects an SQL expression (a string) as the second parameter, but you were supplying it a FeatureSet (the result from the Intersects function)
... View more
08-21-2025
09:21 AM
|
1
|
4
|
1436
|
|
POST
|
You can find that by clicking on the down arrow in the Details section under the URL
... View more
08-20-2025
05:41 AM
|
1
|
2
|
1175
|
|
POST
|
You can use a SQL expression in the Distinct function var fs = FeatureSetByPortalItem(Portal('https://xyzx.arcgis.com/'), 'xyzxyzx', 0, ['StartDateTime'], false);
return Distinct(fs,{
name: "StartDateTime",
expression: "CAST(StartDateTime as DATE)"
}) However, if your dates are in the Western Hemisphere, then you have to add the correct number of hours to correct for the UTC offset. var fs = FeatureSetByPortalItem(Portal('https://xyzx.arcgis.com/'), 'xyzxyzx', 0, ['StartDateTime'], false);
var dates = Distinct(fs,{
name: "StartDateTime",
expression: "CAST(StartDateTime as DATE)"
});
var features = [];
var fields = [{ name: "Date", type: "esriFieldTypeDate" }];
for (var d in dates) {
Push(features, { attributes: { Date: DateAdd(d.StartDateTime, 4, "hours") } }); //I'm in the US Eastern Time Zone, so I have to add 4 hours
}
return FeatureSet({ fields: fields, features: features });
... View more
08-19-2025
06:28 AM
|
1
|
0
|
613
|
|
POST
|
Click the three dots in the upper left corner of the map element and the gear icon to open the configuration dialog
... View more
08-13-2025
11:38 AM
|
0
|
0
|
748
|
|
POST
|
Since you haven't specified the units for the DateDiff function, it's going to return the difference in milliseconds. What happens if you format to return it in years (and round it to two decimal places)? Round(DateDiff(Now(), $feature.Manufacture_date, 'years'), 2);
... View more
08-13-2025
11:35 AM
|
2
|
1
|
1650
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 02-04-2025 06:39 AM | |
| 1 | 2 weeks ago | |
| 1 | 04-10-2026 12:01 PM | |
| 1 | 04-13-2026 09:11 AM | |
| 1 | 10-11-2023 06:18 AM |
| Online Status |
Offline
|
| Date Last Visited |
yesterday
|