nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

GUID/Related Table Question for Existing Data

KamillePreto

I have an existing Dashboard with Construction data on it. I've encountered a lot of issues with this data specifically where the data would just go corrupt suddenly and the dashboard would be unavailable. I've had to re-build this dashboard multiple times over the years, and recently, I just re-created the data from scratch to see if it would resolve the reoccurring issues.

Now that everything is resolved (yay!)... long story short, I don't want to modify anything unnecessarily, especially if it sends my data into a tailspin again. So here is my question.

The intention of this dashboard is to see where our money is spent on Construction. The data is formatted by Funding Source, as you can see below. Many projects span multiple municipalities, so I have one field that just lists them out so they can be displayed on the pop-up.

Recently, an Administrator asked if we could display this data (in another dashboard) by Municipality. So think of bar charts rather than the $$ boxes. However, the data is not set up to display this currently, since the Municipal field I have just lists them out.

What is the easiest way to go about this? Like I said, I don't want to unnecessarily edit the data unless I have to. In the past, someone helped me add a Related Table and I took each construction project's GUID and entered it into the Related Table and typed the municipality there. But that was an older dataset, and I didn't think we needed it this time around.

If you're still reading, thanks for sticking around. I could really use the help on this one. The GUID/Related Table concept is really confusing for me. If there's an easier way, I'll take it!

Find more posts tagged with

ArcGIS Enterprise

Accepted answers

jcarlson

Well, if it's just breaking up that field, a Data Expression could handle this.

Check out this example, which takes a comma-delimited field and breaks it up to display the chart correctly. The same idea could as easily apply to a bar chart, or even to individual indicators, etc.

If you need the chart to be dynamic, the expression would need a bit of reworking. But to just get the per-municipality count, this will do it.

All comments

jcarlson

By the way, there's a little "code expression" button here if you expand the toolbar:

Anyway, the problem with line 32 is that your fields array should have a comma between each item. Line 31 ends without a comma, so there's nothing telling the expression that the two lines are different items in the array. Line 22 likewise needs a comma at the end.

If it's complaining about your Portal URL, I'd just make sure that you're using the same web address that goes to your GIS portal. It often (but not always) ends with /portal.

KamillePreto

Thank you Josh.

Again, data expressions are totally new for me. This is like looking a foreign language almost. I understand it a little bit from some sql I've done in the past. But anyway, I think I put in everything that I need. Do you mind looking it over and telling me if I'm missing anything? It says there's unexpected string in Line 23 (parse error), and there's also an "x" on line 32. So I must've done something incorrectly.

I've done screenshots this time. Sorry I can't get it full screen.

It also told me yesterday that our Portal URL was incorrect, which it's not. So I need to figure that out as well.

jcarlson

Got it. To include that attribute, you just need to have it piped into the output dicts.

First, make sure that your status is one of the requested fields in your FeatureSetByPortalItem function. I'll assume the field is named "Status" for the rest of this.

Next, when you are iterating over the fs object and splitting, include the status as one of the attributes:

feat = {
    'attributes': {
        'split_choices': Trim(split_array[i]),
        'status': f['Status'] // or DomainName(f, 'Status'), if there's a real domain on it
    }
}

In order to hold that attribute, you'll also need to define a field in the choicesDict object:

var choicesDict = {
    'fields': [
        {'name': 'split_choices', 'type': 'esriFieldTypeString'},
        {'name': 'status', 'type': 'esriFieldTypeString'}
    ]

Finally, include the status as one of your grouped fields in the final GroupBy function.

// Return featureset after grouping by hazard types.
return GroupBy(
    fs_dict,
    ['split_choices', 'Status'],
    [{name: 'split_count', expression: 'split_choices', statistic: 'COUNT'}]
);

In your chart settings, you'll still be able to tell it to group the features based on the split_choices field, but you can split each series by the status, or even filter your data based on the status field. That way you'll be able to use the same data expression for each of those charts.

KamillePreto

Thank you again!

How about my other question from my last comment? I'll post it here:

A side note: I also will need to add something in the code that basically says to only include features that fall under our "Status" Domain as: Planning, In Design, and In Construction. We also have Substantial Completion, Final Completion and Closed with Finance that are considered "completed" projects, and will not be on this bar chart. I think I'll need to have two charts - one for the first 3 categories, and another for the last 3 categories. Hopefully this makes sense. I basically need to query the data for the bar chart to only include specific categories of projects.

jcarlson

Ah, whoops! Looks like I didn't test this one enough, there's a misplaced bracket.

Add a second bracket to line 23, and remove one of the three brackets on line 25.

KamillePreto

Hi Josh,

Sorry for multiple messages.

I pasted in the code from the website you sent me and it says "Unable to parse script. Check your syntax". So I just continued modifying the script anyway, but it still says it for Line 24. Would you be able to look it over and let me know what you think? I put Line 24 in bold. If a screenshot is easier since it has the spacing, let me know.

// Reference layer using the FeatureSetByPortalItem() method.
var portal = Portal('https://sql2017.w2k.co.camden.nj.us/')
var fs = FeatureSetByPortalItem(
portal,
'7685831f1c4c4592ac7930bda21c9085',
0,
['Municipalities'],
false
);

// Create empty array for features and feat object
var features = [];
var feat;

// Split comma separated hazard types and store in dictionary.
for (var feature in fs) {
var split_array = Split(feature["Municipalities"], ',')
var count_arr = Count(split_array)
for(var i = 0; i < count_arr; i++ ){
feat = {
'attributes': {
'split_choices': Trim(split_array[i])
}
Push(features, feat);
}}}

// Empty dictionary to capture each hazard reported as separate rows.
var choicesDict = {
'fields': [
{ 'name': 'split_choices', 'type': 'esriFieldTypeString'}],
'geometryType': '',
'features': features
};

// Convert dictionary to featureSet.
var fs_dict = FeatureSet(Text(choicesDict));

// Return featureset after grouping by hazard types.
return GroupBy(fs_dict, ['split_choices'],
[{ name: 'split_count', expression: 'split_choices', statistic: 'COUNT' }]);

Thank you again for your time and help.

jcarlson

It's a lot to wrap your head around initially, but once you get the hang of them, Data Expressions aren't too bad.

You'll need to create the Data Expression as though it were a new layer in your dashboard. When you add a new widget, you can see a section at the bottom for data expressions, and a button to add a new one.

Click to add a new expression, and that is where you would put all the code. And yes, you'll need to swap in your own values for:

Portal URL (line 2)
ItemID (line 5)
Layer Index (line 6)
Required Fields (line 7)
Municipalities field name (line 17)

KamillePreto

Oh wow, that example does look like it could work! This looks great.

I assume that I would need to replace most of the data within the expression, right? I haven't ever played with anything this complex, but I understand the general idea of creating queries/etc.

Where would I enter this expression? Within the widget configurations?

Thank you again for all of your help with this.

jcarlson

Well, if it's just breaking up that field, a Data Expression could handle this.

Check out this example, which takes a comma-delimited field and breaks it up to display the chart correctly. The same idea could as easily apply to a bar chart, or even to individual indicators, etc.

If you need the chart to be dynamic, the expression would need a bit of reworking. But to just get the per-municipality count, this will do it.

KamillePreto

Hi Josh,

Thank you for getting back to me on this, I appreciate it.

No, we are not tracking cost per Municipality. It's just the overall cost per project.

For the new Dashboard, they want the same data displayed (minus the cost widgets on the left), and they just want to see "X Municipality has 3 projects", "X Municipality has 7 projects" - displayed in chart form, such as a bar chart. So that we can see where the focus is.

As I stated in the initial post, I previously had a Related Table linked to the data where I did this via the GUID & Related Table, but I was not the one who set it up (and do not have access to this person moving forward). And since I re-created the data from scratch, I did not set it up that way since Municipal counts were not requested from Administration. But now they are.

Here's an example of what the data looks like:

Construction Data.JPG

jcarlson

When a project spans municipalities, are you somehow tracking the costs proportionate to each? Or does your admin just want to see "X projects were in / partially in Municipality Y"?

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.