POST
|
I figured it out! Pretty much already had it in my code - referencing the request itself is pretty easy inside the "data" function. In this way, the original sort order can be set, AND the user can then sort themselves, but it still works with server-side functioning and more than 1,000 rows (which I had previously taken care of by the dataSrc function). I already had the first two lines, just added the d.orderByFields line: data: function(d) { // this is where datatables add url params for server-side processing d.resultOffset = d.start; d.resultRecordCount = d.length; //reference the request against the column array to customize the sort d.orderByFields = colArr[d.order[0].column] +" "+ d.order[0].dir; return d; }
... View more
03-09-2020
10:54 AM
|
0
|
1
|
3428
|
POST
|
Yeah, I originally specified the ordering in the REST query but didn't like having to then mess with the native styles. Sorry I edited my original before seeing your response...if I do client-side, I am limited to the 1,000 features returned by the server. So yes, I'm trying to do that concatenation you mention, but I don't know how to "snoop" on the order requested by the user when creating that concatenation. I'm searching for examples of where the DataTables request can be self-referenced.
... View more
03-09-2020
10:34 AM
|
0
|
2
|
3428
|
POST
|
William, this is a great example. I'm currently struggling with getting DataTables to alter the AJAX request for sorting when my REST endpoint expects "orderByFields = <FIELD><ASC/DESC>", and DataTables just sends the two "order" params defined at https://datatables.net/manual/server-side If I could somehow self-reference those options in the "data" function, I could customize the request and make it work. But your example makes me think you got it working WITHOUT customization. Maybe that's because you're not using the serverSide option and have less than the typical Esri REST-endpoint limit of 1,000 rows. Could you confirm that's true? Thanks --mike
... View more
03-09-2020
10:01 AM
|
0
|
4
|
3427
|
POST
|
Did you ever figure this out? I am working with 4.14 and the first time after a search the popup appears with no content. The second time through it works as expected.
... View more
02-12-2020
11:20 AM
|
0
|
0
|
695
|
POST
|
Super cool. I logged in just to come here and say "thanks" for this solution - while I actually couldn't get it working I think I was only about a few steps away from getting it there. Since I created my popup at the same time as the MapView, I don't think the variable was quite right. BUT it led me to look at the Property Overview: Popup | ArcGIS API for JavaScript 4.14 And from there I saw that I could set collapseEnabled: false, on the popup during construction, and achieve the same end result! Cheers, mike
... View more
02-05-2020
01:39 PM
|
2
|
0
|
1823
|
POST
|
Jeez, found them. WHY does it always take ten (Google) searches to find stuff like this? Service output—ArcGIS REST API: World Geocoding Service | ArcGIS for Developers
... View more
02-16-2018
10:10 AM
|
5
|
0
|
4958
|
POST
|
Yeah, none of the docs above are what I'm looking for, either. It's pretty easy to force a bad token so I know at least one error code out of the REST API: {"error":{"code":498,"message":"Invalid Token","details":[]}} but...seriously, there's no others? Pretty sure a timeout can happen too. Gotta be a list somewhere.
... View more
02-16-2018
10:08 AM
|
0
|
2
|
4958
|
POST
|
Awesome! Just the answer I needed, thanks for posting this!!!
... View more
02-09-2018
09:55 AM
|
0
|
0
|
1926
|
POST
|
OK, here's what I had to do to fix this issue - hopefully you have your locator source data to do the same. First, check to see if your locator source data (ie addressable streets, address points, parcels, etc) are stored with Z and M coordinates. If they are, get rid of those geometry elements by exporting from one feature class to another, but disabling Z and M values in your Geoprocessing Environment variables. Then, rebuild your locators on the new source data. After doing that, I was able to geocode against my new locators and the outputs are just points - which work everywhere more consistently!
... View more
06-07-2016
01:41 PM
|
1
|
3
|
1042
|
POST
|
I'm pretty much having this exact same problem. It may be something going on with 10.4, since I recently upgraded, and didn't have this problem before. I also thought of the Geoprocessing environment settings - and my change made no difference, just as you found. Regarding your aside question, the only way I can think of that happening is if it were also tied with another candidate, and you chose NOT to match if candidates were tied.
... View more
05-31-2016
10:08 AM
|
1
|
1
|
1042
|
POST
|
Do either of you know if there is a bug report for this, and/or if it is fixed in 10.2? I know it still says "Test Connection" in the wizard, which is totally ambiguous. If it really needs that account to maintain the connection to the domain controller, it's doing more than "testing", isn't it?!? I guess it can also depend on the AD group policy, but it certainly seems like a flimsy setup.
... View more
02-05-2015
07:16 AM
|
0
|
0
|
425
|