POST
|
The service definitions don't need to be shared. If you share a link to the Web Map I can probably tell you what is causing the login prompt. I basically look at the network requests via Chrome/Firefox Developer Tools and look for one that returns a token required message. From there you can typically tell what specific request is causing the prompt.
... View more
11-09-2020
10:06 AM
|
0
|
4
|
271
|
POST
|
Thanks for the quick reply Russell - appreciate the updates.
... View more
11-09-2020
10:03 AM
|
0
|
0
|
61
|
POST
|
Hey Nigel - the same security applies for Web Maps created in either viewer. It's likely that something in the Web Map is not shared publicly, e.g. layer/basemap/locator/print service. Looking at the Web Map item details page can be a good way to look through the layers to ensure they are all shared appropriately.
... View more
11-09-2020
06:57 AM
|
0
|
6
|
271
|
POST
|
Hey guys, I really enjoy using the new Map Viewer - great job. A few pieces of feedback that I came across last week: One of those things that when you see it, it's obvious, but it took a second look to find! To alter the basemap properties (I was looking for transparency), you have to click in the 'Current basemap' box highlighted below to open the properties panel. I think the default behaviour should be that when you select a different basemap, the sub-page opens with the basemap property options Turning on/off all layers by holding Ctrl and clicking on the visibility button does not seem to be implemented. This is really useful when dealing with many layers, so I'm hoping it's on the TODO list! Similar to above, I would love to be able to select multiple layers using Ctrl, click and drag when moving them around/into group layers In the Scene Viewer you have an option to choose how layers within a group layer can be selected (checkbox/radio/merge/hidden) Mikie
... View more
11-09-2020
06:53 AM
|
0
|
2
|
355
|
BLOG
|
Hi Zhifang, Ah I was basing it off this. I just did some testing, and got it to work with URL's with just over 5650 characters. URLs with between 5650 and approx 8000 returned a HTTP 400 error as below: 8000 characters and above returned either a 413 error from CloudFront as below: Or a server error: All testing done in Chrome. Appreciate your help with this. As I said, I have got around this by using relevancy in the form along with hiding groups. But a hideBlankFields option/extended parameter character allowances via the API would also be very useful. Thanks, Mikie
... View more
04-28-2020
08:20 AM
|
0
|
0
|
1872
|
BLOG
|
Hi Zhifang, Thanks for following up. In this case hide parameters that take up 90% of the URL characters. Having to insert field: before every field name takes up a decent amount of characters. Perhaps the length of the parameter could be minimized by adding a hideFields parameter like: hideFields=field1,field2,field3 Having said that currently the URL I want to use stands at over 10,000 characters so this probably wouldn't be sufficient anyway. I am going to work something into the form itself with groups to minimize the number of fields I need to input, but it does mean I won't be able to hide all of the fields I want to hide, and will require additional coding to setup custom relevancy options. Re: Post requests - I was thinking that behind the scenes the API may be able to handle larger requests via post. Thanks again, Mikie
... View more
04-24-2020
10:30 AM
|
0
|
0
|
1872
|
IDEA
|
As things stand, there are some very useful web form URL parameters available for use in the web version of Survey123, as documented here. I would like to build on these parameters as follows: hideBlankFields: When in view mode, hide null/blank records so they do not appear in the form display. It would bring equivalency with the features in the Survey123 website Data tab, where when you click on a record, only records with values appear. This could also then be exposed for use in the JavaScript API, as discussed here.
... View more
04-22-2020
01:03 PM
|
3
|
0
|
209
|
BLOG
|
Thanks a lot Zhifang - I have just logged this through support channels also. Idea logged here: Enhancement Number: TBC
... View more
04-22-2020
11:28 AM
|
0
|
0
|
1872
|
BLOG
|
A side question...can parameters be passed as post requests to the web form, or just as get requests? I can see myself exceeding the url length limit given how many fields I want to hide.
... View more
04-15-2020
02:34 PM
|
0
|
0
|
1872
|
BLOG
|
For the Javascript API and URL parameters, I would love to have an option to only view fields that are not blank in the form itself. Some datasets that I use have hundreds of fields, with only 10 or so actually having values. It may be bad database design, but it is not something I have control over. Right now there is a parameter to hide fields which is great. If this could be used in combination with a hideBlankFields parameter it would be very beneficial. I'm working to do this right now with some Javascript, but it would be nice to not be reliant on this 🙂
... View more
04-15-2020
12:45 PM
|
0
|
0
|
1872
|