topic Re: Solution for BUG-000086319. in ArcGIS Web AppBuilder Questions

Solution for BUG-000086319.

LianaSmith — Wed, 08 Jun 2016 14:17:28 GMT

Does anyone have any solution for the bug (#BUG-000086319 Numeric field types within the attribute table in the Web AppBuilder still show the thousand comma that were removed in the webmap in arcgis online)?

In my query results numeric field values have commas that I do not need.

Re: Solution for BUG-000086319.

DanPatterson_Retired — Wed, 08 Jun 2016 18:05:29 GMT

The most recent bug lists for arcmap are here http://downloads.esri.com/support/downloads/other_/1041-IssuesAddressedList.pdf for others, you will have to go to support and examine for previous versions and software.

Re: Solution for BUG-000086319.

MelitaKennedy — Wed, 08 Jun 2016 19:26:23 GMT

What version are you using? I'm seeing that it was verified as fixed in February but that might have been too late to make the March 2016 2.0 release.

Re: Solution for BUG-000086319.

LianaSmith — Wed, 08 Jun 2016 20:00:17 GMT

i have both 1.3 and 2.0. This problem occur in both..

Re: Solution for BUG-000086319.

RobertScheitlin__GISP — Fri, 10 Jun 2016 13:24:04 GMT

Liana,

I have tested in WAB 2.0 and I am not seeing this issue anymore.

Re: Solution for BUG-000086319.

LianaSmith — Fri, 10 Jun 2016 20:19:35 GMT

Robert, I checked again and even created new application, but still get the same ( at the query results some values have commas). I noticed that commas appear only for the values whose format is long integer.

Re: Solution for BUG-000086319.

RobertScheitlin__GISP — Fri, 10 Jun 2016 20:35:00 GMT

Liana,

OK is this only happening with the query widgets results? If so then this is still an issue until the next release around UC time.

Re: Solution for BUG-000086319.

LianaSmith — Mon, 13 Jun 2016 13:29:34 GMT

Robert, it only happens with the query widget results..I have seen that you were giving help to someone else with some changes that could be done in the code. By any chance do you have similar option for WAB 2.0? or 1.3? Thank you!

"There is no configuration in place for this. But you can easily add code to handle this. Open the Query Widget.js file and around line 1131 replace:"

fieldValue = this._tryLocaleNumber(fieldValue);

with:

if(fieldAlias !== "Zip code"){
fieldValue = this._tryLocaleNumber(fieldValue);
}

Re: Solution for BUG-000086319.

RobertScheitlin__GISP — Mon, 13 Jun 2016 13:57:37 GMT

Liana,

Are you now using the developer version?

Re: Solution for BUG-000086319.

LianaSmith — Mon, 13 Jun 2016 14:18:04 GMT

Yes! I had to import it to Developer Edition to be able to change the code

Re: Solution for BUG-000086319.

RobertScheitlin__GISP — Mon, 13 Jun 2016 14:27:41 GMT

Liana,

The code in this thread should work fine then (it is just line 1171 for WAB 2.0):

About query widget - field data type

Re: Solution for BUG-000086319.

LianaSmith — Mon, 13 Jun 2016 14:41:42 GMT

Robert, I changed the code and now the query fails..Could you please check if I did right? I dont know Java Script, so I am not sure if I did it right

Re: Solution for BUG-000086319.

RobertScheitlin__GISP — Mon, 13 Jun 2016 15:45:25 GMT

Liana,

What error do you see in your browsers web console?

Re: Solution for BUG-000086319.

NathanBruce1 — Mon, 05 Dec 2016 14:20:34 GMT

Still occurring for me with the WAB in query results.

Re: Solution for BUG-000086319.

DerekLaw — Mon, 05 Dec 2016 17:44:27 GMT

Hi Nathan,

Can you please contact Esri Tech Support so we can get some repro steps and investigate further to see if this is still an issue?

Thanks,

Re: Solution for BUG-000086319.

NathanBruce1 — Mon, 12 Dec 2016 18:08:27 GMT

I contacted ESRI Canada support, who is investigating and will report to AGOL development.

Here are some things that I learned that may help others. The web map that the WAB is based on was created before the update to fix this original bug, when I create a new WAB from the same map, I still see the comma's appear if the query is set to "unique"; but it its set to "value" the issue is fixed. If your application data or users are a little forgiving, you could switch the field that's giving you trouble from number to text to get around the comma issue.

Re: Solution for BUG-000086319.

KatherineWright — Thu, 02 Feb 2017 19:38:26 GMT

Still happening as of February 2017. I will make a point to ask about this at the DevSummit next month.

Re: Solution for BUG-000086319.

DerekLaw — Fri, 03 Feb 2017 18:03:10 GMT

Hi Katherine,

Can you please contact Esri Tech Support so we can get some repro steps and investigate further to see if this is still an issue?

Thanks,