Hello,
Since I upgraded from Portal for ArcGIS 11.0 to Portal for ArcGIS 11.1, I can no longer share items with the groups I own... I guess it's a regression as it used to work with 11.0.
I debug a little bit and noticed the following: if you own more than 29 groups configured with "isViewOnly" set to True (Who can contribute content ? => Group owner and managers"), I can no longer share.
Indeed, to retrieve the list of groups that can be shared with, it makes a POST to:
/sharing/rest/community/groups
with the following 'q' parameter:
q: (isviewonly:false OR 0108318c3d144cf5be12837022f7049c OR 0171609ba0ba480fa2cfb40a9a70635f OR 0934e513266d4ddb80e342cd658937bf OR 0c4a52980b94405ca7ac853fd938ca31 OR 15620fa67eac4973818f7789653b66b4 OR ... OR fce1af7d980144999b28c968c4439232)
If you have less than 30 groups, request works if you have 30 or more, it returns:
{"total":0,"start":0,"num":0,"nextStart":0,"results":[]}
At Portal for ArcGIS 11.0, this request was made differently as the groups were not specified in 'q' parameter but the user was specified:
q: (owner:myusername OR isviewonly:false)
Could you please help ?
Thanks,
Nicolas
Solved! Go to Solution.
And here it is @MarleyGeddes ! The following BUG has been logged by support in case you want to take a look:
Thanks
Hi @NicolasGIS - do you think this in anyway has anything to do with what you did here:
with the web adaptor and proxy issues you encountered? And this is probably obvious, but did you try toggling the 'who can share' setting and then try save again?
Hi @DavidColey,
I don't think that it has anything to do with the WebAdaptor bug regarding OAuth (it's fixed on my side by fixing Web Adaptor response at reverse proxy level).
If I configure all my groups with "who can share" configured to "All group members" it works because then the group ids are not included in the 'q' parameter that why I specified this configuration in the bug report.
Of course, I did not change this parameter because I don't want all group members to contribute.
Thanks
No, you clearly can't permanently set to 'All Group Members' and neither could I. Geez, I don't think I've this many upgrade issues with a release before.
From custom print services not working:
to the hosting server not communicating with the datastore:
to your web adaptor issue:
to Data Clients not behaving:
to loss of access to Microsoft Azure Active Directory user store:
to bad behavior of the WMS Services (although there is now a patch for this):
I am scheduled to do my upgrade this weekend but I think I have to pull the plug on that. I have no webgisdr tool because my Federated site name 'agsfed' contains letters that appear in the word 'admin' and so it won't run. I have to depend purely on a snapshot and content backup if anything goes wrong.
And it sure seems like LOTS of things are going wrong.
Thank you for reporting this issue @NicolasGIS.
There is a workaround available to help in this situation. In the case that you have over 29 groups that are configured to only allow group owners and managers to contribute, you can share items to these groups from the group's content page. I know that the likely more popular share item workflows happen from the Content or item details pages, but this is another workflow that does not seem impacted by this issue.
Thanks @MarleyGeddes for your reply and workaround.
Indeed, it does work. But still, you cannot unshare afterward in case of a mistake.
FYI, I have a case opened. Waiting the BUG number.
Thanks !
And here it is @MarleyGeddes ! The following BUG has been logged by support in case you want to take a look:
Thanks
Thank you @NicolasGIS for the BUG number.
Just a note for the workaround that you are able to unshare items from the Group's Content page by selecting the item(s) and clicking the "remove from group" option on the page (pictured below). Although this workaround is not ideal, I want to make sure you have the tools to continue your work.
Thanks,
Marley
Edit: As per below this is being addressed in a patch in Q4 2023.
---------
Ive was informed via support that this bug will not be fixed for Enterprise 11.1 and the solution is to upgrade to 11.2 when it comes out. However that turned out to not be the case and this will be addressed in an upcoming patch.
Hi @Trevor_Hart I acknowledge that there was a miscommunication regarding the status of this defect and patch. In addition to the aforementioned workaround for BUG-000158232, this defect is planned to be addressed in an 11.1 patch tentatively scheduled for release in Q4 2023.
Regards,
Kaitlyn