POST
|
This looks like an oversight by ESRI - in that the layer files are not modified to point to the collaboration's replicated workspace (at the point when a replicated collaboration is instigated) - they are still fixed to point to the original location in AGOL. It would be nice if ESRI could fix this so that layer files are modified when a collaboration replication takes place.
... View more
3 weeks ago
|
2
|
0
|
47
|
POST
|
Did this get fixed in 2.7 - I don't see the text about "KNOWN LIMITS"?
... View more
a month ago
|
0
|
0
|
101
|
POST
|
Thanks Kirk - it looks like it might be what we want but sadly I don't think this will work in our case. Its just frustrating that I am finding roadblocks when coding with this limited API - I knew this would happen after being spoiled with ArcObjects.
... View more
01-25-2021
06:14 AM
|
0
|
0
|
31
|
POST
|
Thats a shame - is there something we can do to get this functionality exposed? It's a bit of a roadblock currently for my addin as I don't think having the OAuth prompt dialog is a nice user experience.
... View more
01-22-2021
12:04 PM
|
0
|
2
|
57
|
POST
|
Out of interest (and necessity) is there a way to sign in to a Portal with specific user credentials i.e. a username and password via the SDK?
... View more
01-22-2021
07:04 AM
|
0
|
4
|
299
|
POST
|
Yeh, I'm not going to hard code - I'll put it in a setting thats user configurable - the credentials can always be changed or revoked on our side.
... View more
01-22-2021
01:19 AM
|
0
|
0
|
301
|
POST
|
ahhh, I think I know what you're getting at now. I have remembered that you can be logged into your Enterprise Portal AND it be your active Portal. Also you can be signed into another Portal (not active portal though) and this will be the ArcGIS Online Portal (www.arcgis.com). I think if I can, in code, detect the user is logged in as Enterprise and maintain it as the active portal, has a collaboration and then can sign into ArcGIS Online (hard-coded, not great but it's the best I can do at the moment) then that should work. This will allow the user to work in a way where they don't need to manually login to AGOL.
... View more
01-21-2021
09:29 AM
|
0
|
0
|
317
|
POST
|
Only when the user is trying to add data from a collaboration - as Pro will prompt the user for credentials - which is what we don't want.
... View more
01-21-2021
08:58 AM
|
0
|
0
|
321
|
POST
|
The subtle thing here is: Red Company is already logged in to Red Company's Enterprise Portal - they want to stay logged in here, they don't want to explicitly log into Blue Company's AGOL Portal (they need to see all Red Company's assets and see the collaboration assets via Blue Company) - but Pro forces the user to key in the credentials for that Online Portal if they want to actually add the data into the map (a little dialog window appears asking for credentials). This is not a good UX. I need this to be a slick single sign on process - i.e so the user doesn't have to remember credentials for Blue Company but can stay logged into their active Enterprise Portal at all times i.e. no switching of active portals.
... View more
01-21-2021
08:42 AM
|
0
|
0
|
323
|
POST
|
Hi Here is the scenario (I have written it as a basic story just to make it easier to envisage the problem): We have some content stored in our company AGOL account (lets call this company Blue Company Ltd) , in a group with permissions given to it with the following credentials: FooUser FooSecretPassword Another company (called Red Company Ltd) - would really like to see this data in Blue Company's AGOL via their Enterprise Portal by using a collaboration. Both companies agree the collaboration and everything is sweet. Blue Company also says, use this add-in to add our data in from our AGOL, it's got lots of nice tools to allow you to search for data and other exciting things. A user in Red Company, called Billy, opens Pro and signs into Red Company enterprise portal, he also uses the add-in provided by Blue Company - he can see the data that is shared by Blue Company in the add-in and he tries to add it to the map. 😡 Now Billy is mad, because when he tries to add the data, it prompts him for credentials for AGOL that only Blue Company knows about and they forgot to tell him and they didn't realise that they missed out that whole bit of functionality anyway! How embarrassing! Billy complains to Blue Company about this and the developers frantically try to find in a solution to Billy's problem. ....so there are 2 main questions: 1. In the Pro SDK can you code in the credentials before you try to add data into the map (from a group in AGOL which is shared in a collaboration)? This would be nice, in order to save the user having to remember the credentials every time they want to add data/use the add-in, especially if its been a while between sessions (I appreciate there is some long lived token here or something). 2. The credentials that you are prompted for are stored in Pro somewhere, in a token or cookie or something, and I have no idea how to reset that. I would like to test my code as if the user has used the add-in for the first time and is trying to add data also for the first time. How can I do this? Code example The following is where I envisage any credential info going (perhaps?) when I try to add data from portal: public static async Task AddLayer(string layerId) { FeatureLayer featureLayer = null; Item testLayer = ItemFactory.Instance.Create(layerId, ItemFactory.ItemType.PortalItem); await QueuedTask.Run(() => { if (LayerFactory.Instance.CanCreateLayerFrom(testLayer)) { featureLayer = LayerFactory.Instance.CreateLayer(testLayer, MapView.Active.Map, 0) as FeatureLayer; } else { log.Error($"Failed to add layer {layerId}"); } }); return featureLayer; }
... View more
01-21-2021
07:16 AM
|
1
|
12
|
392
|
Online Status |
Offline
|
Date Last Visited |
3 weeks ago
|