Latest Contributions by MichaelRobb

Hi Derek, Thought I would inquire specifics about named users in Portal while Portal is Federated with ArcGIS Server.  Portal has IWA incorporated for Active Directory - Windows Authentication Scenario.  A web application which sits on IIS - a web server - (anonymous enabled - so Portal can control it) consumes as web map on Portal. This web map is shared to 'everyone'. This Web Map in portal contains several layers, lets say 10 for this example. (so 10 services running on ArcGIS Server, for example) Out of the 10, 8 are shared 'everyone' (public) on portal.  2 of layers in the map sit in a group and a AD Group/Role  is only able to see the layers in portal (not shared to 'everyone').  I am aware of a Nimbus regarding nothing showing up on the web application, but what I want to know is: 'Joe User' needs access to the Group layers (2 layers that are sensitive) and is apart of that Group in AD. Will a named user be required for JOE to see the non-public layers (the sensitive layers)? If so, Lets say a company has 300 people that need to see this sensitive information out of 10,000. does that mean 300 named users are needed to be registered with Portal so that the web app loads the 2 layers for these users? I was hoping the users that should not see the 2 layers would simply see the remaining 8 layers open to the public (a 401 happens in the background but user does not know)... but a bug seems to be hindering that, this is a separate issue of course. (ref # Bug -000087825) I have had zero issues with ArcGIS Server AD enabled and applying Roles to specific Services consumed by apps... but Federated Server with Portal poses some questions... (as ArcGIS Server licensing is based on Core, not named users).  I greatly appreciate your time in explaining this! ... View more

If you are using a StoryMap, the Story Application as well as the Web Apps and Web Maps used in the Story map must all be 'Everyone' shared. I understand what you are looking for now though it still does not require two web maps (sliding two entire web maps would also solve it, but with greater complexity). It just requires customizing the Slide widget to be able to show and hide two selected layers (composite layers or otherwise). ... View more

The above StoryMap link is not set to 'everyone' aka Public. ... View more

Hi Kenneth, Sorry I misunderstood what you were trying to accomplish. Effectively, you are looking for swipe to 'hide' one layer and at the same time 'show' the other.  This is not feasible out of the box.  ... View more

How does one learn WABde as much as you have? Thanks for showing that a simple selector bit of code is there and simply needs to be removed.  This of course means I can select TIME only or DATE only at any instance.  , {           selector: 'date'         } ... View more

I  still dont see the reason for two 'maps'.  If I understand this correctly, you are just talking about two groups of layers. Group them - Now and Proposed and publish as such. In the Now group you have your now fire station layers (plural) In the Proposed Group you have your new fire station layers (plural) The Swipe tool will work with each group as the swipe tool looks at the base level of each item in the TOC (LayerList) ... View more

Here is a screen shot of the Attribute Table in the same Test Web App.. ... View more

Perhaps this works in Version 1.3 and not in 1.2. (sigh) I just tried a new blank new Web App, and get the same result (no TIME). ... View more

Then something is wrong as the field contains Date/Time information as shown above when enabling with the custom popup. ... View more

makes sense.  So I need to change the query code to be able to include Time?  I dont see any configuration ability in the Query Widget to also have time be included in date field calls. Results settings only has the following: ... View more

Hi Kenneth what would be the business case to require a swipe of two maps?  If the swipe tool is able to swipe layers?  ... View more

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. ... View more

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; ... View more

Nope, does not work. Line numbers dont match either. There is only 1601 lines in the apps\##\widgets\AttributeTable\Widget.js ... View more