topic Re: Can attribute table results be limited to map extent by default? in ArcGIS Web AppBuilder Questions

Can attribute table results be limited to map extent by default?

MikeMartin — Thu, 05 Feb 2015 18:29:04 GMT

I do not want all records of a layer's attribute table to be loaded into the attribute table. Can the config_Attribute Table.json be modified to limit results to the map extent by default, and only when the layer's scale range has been reached? Thanks.

Re: Can attribute table results be limited to map extent by default?

RebeccaStrauch__GISP — Thu, 05 Feb 2015 19:21:14 GMT

I have the same question....specifically in the WAB dev edition for me. And using some of Robert Scheitlin, GISP‌ custom widgets.

Re: Can attribute table results be limited to map extent by default?

RobertScheitlin__GISP — Thu, 05 Feb 2015 20:55:20 GMT

Mike and Rebecca,

There is not configuration option for this but it is a really simple one line code change if you are using the WAB Dev version.

client\stemapp\widgets\AttributeTable\widget.js line 185.

this.matchingMap = false;

change to:

this.matchingMap = true;

Re: Can attribute table results be limited to map extent by default?

RebeccaStrauch__GISP — Thu, 05 Feb 2015 21:50:10 GMT

Robert, that worked great.

Note: Of course it does not transfer forward to existing apps, so if anyone else uses this, remember to also update your \server\apps\<app#>\widgets\AttributeTable\widget.js

Interesting observation of odd behavior, even though it definitely works, the Options checkbox started off as unchecked. Checking didn't seem to change anything the first time...but doing it a few times did. So, the togle timing is a bit strange, but not an issue in my opinion, since I would rather have it always filtered.

EDITED: Not totally strange behavior, its just the initial checkbox isn't checked. After code modification, firing up the app and revieiwing attribute table:

- filter box unchecked, but table filtered (minor graphical issue)

- manually check the box - table filtered, as expected

- manualy uncheck the box - table goes back to being unfiltered.

so, just a very minor checkbox thing.

I can't mark your answer as "correct", but hopefully Mike will after he's tested.

Re: Can attribute table results be limited to map extent by default?

MikeMartin — Fri, 06 Feb 2015 11:37:25 GMT

That is beautiful! Thank you Robert. Worked like a charm. I appreciate your help. Thanks also Rebecca.

Re: Can attribute table results be limited to map extent by default?

NicholasBarger — Mon, 15 Jun 2015 19:04:17 GMT

You can also change the following line of code so that the box appears checked.

line 1963 this.matchingcheckbox=true

This will keep the functionality consistent... i.e. you won't have to check the box and uncheck the box to turn off the spatial filter

Re: Can attribute table results be limited to map extent by default?

MichaelPotter1 — Wed, 17 Jun 2015 16:21:30 GMT

Does the Attribute Table widget limit the results when the layer's scale range has not been reached?

Regardless of whether I am using a Web Map or Local Layers, my Attribute Table displays all features in that extent, even if the layer is turned off and not yet at a visible scale range.

Re: Can attribute table results be limited to map extent by default?

MikeMartin — Thu, 18 Jun 2015 10:48:39 GMT

I see the same results as you, Michael. The attribute table displays all records within the map extent, regardless of scale dependency or layer visibility. I'll leave it to experts (of which I am not) to say whether or not that can be adjusted.

Re: Can attribute table results be limited to map extent by default?

NicholasBarger — Thu, 18 Jun 2015 11:11:48 GMT

Yes it can…. Change the following lines of code to default the attribute table to visible extent

*Check the filter by Map Extent by default.

1. Attribute Widget.js

2. Change Line 198 this.matchingmap= true

3. Change line 1963 this.matchingcheckbox=true

~ Nick

Re: Can attribute table results be limited to map extent by default?

MichaelPotter1 — Thu, 18 Jun 2015 21:34:29 GMT

Thanks Nick,

I did change this and it does work for only displaying data in your current extent by default.

However, if the data has a scale dependency and is not currently visible at that particular scale or is turn off in your layer list then the data is still listed in the Attribute Table.

Ideally, similar to how the Flex version of the Attribute Table works, if a layer is not turned on then the tab for that layer does not display in the Attribute table and if the layer is not at the visible scale then no data for that layer displays in the Attribute Table(fields are greyed out and "Layer is out of scale range" is displayed"), see image below.

Hope this makes sense.

Regards

Re: Can attribute table results be limited to map extent by default?

Anonymous User — Wed, 16 Dec 2015 16:38:24 GMT

Michael Potter et al does the WAB 1.3 Attrib Widget respect scale dependency?

Re: Can attribute table results be limited to map extent by default?

MichaelPotter1 — Thu, 17 Dec 2015 15:29:47 GMT

Kevin,

I just finished testing and 1.3 still does not respect scale dependency or layers that are turned off.

I was really hoping 1.3 would provide this functionality but it does not look good.

Regards,

Michael

Re: Can attribute table results be limited to map extent by default?

MichaelRobb — Thu, 17 Dec 2015 16:19:34 GMT

Nope, does not work.

Line numbers dont match either. There is only 1601 lines in the apps\##\widgets\AttributeTable\Widget.js

Re: Can attribute table results be limited to map extent by default?

RobertScheitlin__GISP — Thu, 17 Dec 2015 17:06:42 GMT

Michael,

In WAB 1.3 you will find the line to change at 148 and line 1159 (both are currently true so if you do not want the widget to use the maps extent by default then make them false).

Re: Can attribute table results be limited to map extent by default?

MichaelRobb — Thu, 17 Dec 2015 18:40:30 GMT

Hi Robert,
Always a pleasure reading your posts! Very informative.

I am not using 1.3. Using 1.2

Id rather know the line of code rather than the LN for reference. As those LN do no good for 1.2

The below was changed as per njbarger post, which failed to work

changed this.matchingMap = false; TO this.matchingMap = true;

And

Changed this.matchingCheckBox = null; TO this.matchingCheckBox = true;

Re: Can attribute table results be limited to map extent by default?

NicholasBarger — Thu, 17 Dec 2015 18:59:25 GMT

Hi Michael,

Those sections of code were for 1.1. There may be something else in the code that is controlling the behavior. I would make sure you clear your browser cache and I've also found I need to back out of WAB builder and get back into after making certain changes.

Re: Can attribute table results be limited to map extent by default?

NicholasBarger — Thu, 17 Dec 2015 19:12:20 GMT

Ok...so a follow-up to the previous message. I changed line 143 this.matchingCheckBox = null; to this this.matchingCheckBox = true; and line 145 from this.matchingMap = false; to this this.matchingMap = true; and it works. The thing I am missing is that the check box does not show as being checked. When I click on the check box the record count doesn't change. When I uncheck the box the record count shows everything in the dataset.

Re: Can attribute table results be limited to map extent by default?

RobertScheitlin__GISP — Thu, 17 Dec 2015 19:16:17 GMT

Michael,

OK in 1.2

line 143: this.matchingCheckBox = null; should Not be changed.
line 145: this.matchingMap = false; should be changed to true
line 1031: checked: false, should be changed to true

Tested and working in WAB 1.2

Re: Can attribute table results be limited to map extent by default?

MichaelRobb — Thu, 17 Dec 2015 20:55:24 GMT

That worked!

File: Server\apps\##\widgets\AttributeTable\Widget.js

Change code this.matchingMap = false; TO this.matchingMap = True; (ln 145 in version 1.2)

Change code checked: false, TO checked: true, (ln 1031 in version 1.2)

Filter my Map Extent is enabled (now default) when application is launched.

Re: Can attribute table results be limited to map extent by default?

GeorgeKatsambas — Fri, 25 Jan 2019 16:33:08 GMT

In WAB 2.11 where is this option?

this.matchingMap = false;

change to:

this.matchingMap = true;