-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assigning collection to large result dataset malfunctioning #260
Comments
Hi, Thanks on behalf of the BLM Landscape Approach Data Portal Team |
implemented in 1.2.8 |
Hi. Thanks for fixing this in the next version. We have recently upgraded
to 1.2.7 a few months ago. It is non-trivial for us to upgrade again. Is
there a chance we can get the class files and related files if any to
implement this in 1.2.7? We have done this with patches in the past.
Thanks,
Rick
…On Tue, Jun 13, 2017 at 4:01 PM, ZhongPing Guo ***@***.***> wrote:
implemented in 1.2.8
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#260 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFLct2QB0Gb0MH55oGZTxW5S9iv93NT-ks5sDwbCgaJpZM4MB9tx>
.
--
Richard M. Bradley
GIS Server Administrator
Sanborn Map Company, Inc.
Ethics Lesson: "Take a moment to figure out whether you'd rather be
praiseworthy but not praised, or praised but not praiseworthy."
Nicholas Nassim Taleb author of "The Black Swan"
|
yes we can provide it as a quick fix. |
Here is the url for downloading the fix: |
In addition to issue #176 (which is closed) we are seeing a somewhat similar problem when we assign a collection to a large record set.
The "Apply action to entire result set" does not function when performing the "Share With" action. No records are modified with the intended collection when this option is selected. (Refer to the now closed issue #64. The "Share with" action does work but only on one page of a result set and when the "Apply action to entire result set" is left unchecked. See below:
This behavior is not the same as when performing other actions with "Apply action to entire result set" is checked - like setting records to Approved, or setting restrictions. It seems that it works with other pre-1.2.7 Actions.
As a result of this, in order to apply a collection to a large group of records, the action needs to be performed once on each page in the result set.
This is NOT the same behavior that deals with the "Apply action to entire result set" when the result set is being "FILTERED" by a collection. This is an undesirable behavior that occurs when "SETTING" a collection.
See below:
We are going to be upgrading soon to 1.2.7 and have tested this issue in that version. If a patch to correct this issue could be issued for 1.2.7 that would be great!
The text was updated successfully, but these errors were encountered: