Latest Contributions by KenBuja

This goes back to my previous post How you get the features variable depends on where you're using the Arcade code. It could be using the variable $datastore or $layer. Or you might need to get it from a function like FeatureSetByName or FeatureSetByPortalItem What happens when you use "$datastore"? ... View more

You're using the layer name instead of "$layer" ... View more

The Distinct function for FeatureSets has the syntax Distinct(features, fields) with the "features" variable being a FeatureSet and the "fields" variable being either a single field name or an array of field names. How you get the features variable depends on where you're using the Arcade code. It could be using the variable $datastore or $layer. Or you might need to get it from a function like FeatureSetByName or FeatureSetByPortalItem What do you get if you use this in your code? Distinct($layer, "Peferisana starost")   ... View more

What are you trying to do with this code? This affects what profile variables and functions you're able to use in your code. For example, labeling and visualization gives you a very limited set of profile variables and function bundles for efficiency reasons, whereas field calculations and popups give you more. In any case, you can't use "$Kartirane geoloske jedinice", since that is not a FeatureSet variable. ... View more

You're using the incorrect syntax for the Distinct function for a FeatureSet. It should be  Distinct($layer, 'fieldName') //or Distinct($layer, ['fieldName1', 'fieldName2'])   ... View more

Can you post your code? ... View more

Can you post your code and a sample of your text? ... View more

There is no "Add data" button on the left pane of the current AGOL Dashboard. It does have an "Analytics" button. Are you thinking of Experience Builder or Web AppBuilder with their "Add Data" buttons? ... View more

You can use an Arcade element to do this. In this example I am testing whether a feature has the attribute "Fish and Benthic" (line 14). This field has a domain, so I have to get the Domain Name ( line 12). If the feature does have that attribute, I want the display to contain the five fields in the line 16. Otherwise, it will contain the three fields in line 22. var fields = Schema($feature).fields; var attributes = {}; var fieldInfos = []; function fieldTest(fieldList, fieldName, fieldAlias) { if (Includes(fieldList, fieldAlias)) { attributes[fieldalias] = $feature[fieldName]; Push(fieldInfos, { fieldName: fieldAlias }); } } var code = DomainName($feature, "Survey"); for (var i in fields) { if (code == "Fish and Benthic") fieldTest( ["Site ID", "Fish Status", "Fish Date", "Benthic Status", "Benthic Date"], //the list of fields you'd like if the feature has this attribute fields[i].name, fields[i].Alias ); else fieldTest( ["Site ID", "Fish Status", "Fish Date"], //the list of fields you'd like if the feature doesn't have that attribute fields[i].name, fields[i].alias ); } return { type: "fields", fieldInfos: fieldInfos, attributes: attributes };  These are what the two popups look like   ... View more

I'm seeing all the images   ... View more

Unfortunately, this is not something that can be directly done through Advanced formatting in the Values tab. This is because the Arcade code in there only works with individual rows and not the entire dataset. You would have to create an additional field, which can be done with Arcade in a data expression that powers the table. Then you can use the value for the field to highlight the cell with Advanced formatting with Arcade. This code adds the extra UniqueCount column to your dataset. It does run slowly, but I don't know if that was due to network issues we seem to be having today. I'll have to do some more testing to see if I can make it more efficient. var fs = FeatureSetByPortalItem( Portal("your Portal"), "yourItem", 0, false ); var uniqueField = "your field"; var grouped = GroupBy( fs, uniqueField, { name: "Count", expression: "1", statistic: "COUNT" } ); var fields = Schema(fs)["fields"]; Push(fields, { name: "UniqueCount", type: "esriFieldTypeSmallInteger" }); var temp_dict = { fields: fields, geometryType: "", features: [] }; for (var f in fs) { var attrs = {}; var value; for (var attr in f) { attrs[attr] = f[attr]; if (attr == uniqueField) { value = f[attr]; } } var sql = `${uniqueField} = ${value}`; //var sql = `${uniqueField} = '${value}'` // if uniqueField is a text field attrs.UniqueCount = First(Filter(grouped, sql)).Count; Push(temp_dict["features"], { attributes: attrs }); } return FeatureSet(temp_dict); You don't need to add the UniqueCount field to the Value fields when setting up the table, but you'll use that field in the Advanced formatting tab. In this example, since all the Depth_ft values in my test table have multiple instances, I'm highlighting those that have more than 10 instances in line 1 var bgColor = iif ($datapoint.UniqueCount > 10, '#ff0000', '#ffffff') return { cells: { FIELD_ID: { displayText : Text($datapoint.FIELD_ID), textColor: '', backgroundColor: '', textAlign: 'right', iconName: '', iconAlign: '', iconColor: '', iconOutlineColor: '' }, LAT: { displayText : Text($datapoint.LAT), textColor: '', backgroundColor: '', textAlign: 'right', iconName: '', iconAlign: '', iconColor: '', iconOutlineColor: '' }, LONG: { displayText : Text($datapoint.LONG), textColor: '', backgroundColor: '', textAlign: 'right', iconName: '', iconAlign: '', iconColor: '', iconOutlineColor: '' }, DEPTH_FT: { displayText : Text($datapoint.DEPTH_FT), textColor: '', backgroundColor: bgColor, textAlign: 'right', iconName: '', iconAlign: '', iconColor: '', iconOutlineColor: '' }, } } That yields this table   ... View more