Good Afternoon,I answered my own question. (by reading documentation, go figure)Adding “$top=10000” bypasses the limits.
I am not familiar with conditional mass-update access, but… Since the Mass-Update options are defined at screen level (Studio > UI Designer); you could consider creating a copy of the screen with just 1 of the 2 mass-update options, and controlling (through role > screen options) which users receive which screen.
Hi @STRGoedhart is this for use in an xml business rule? Thank You, Morris @Morris, This will be for a Scheduled Process
Just sharing that We've encountered a similar issue. I did not find a resolution (yet) The problem seems to be specific to aliases created from custom tables.In our experience, when we attempted to join the same table twice to a screen, it gave us the error when using Custom table aliases, but it works perfectly when using Baseline table aliases. example: Tab 1: Utilized the Custom Table directlyTab 2: Utilized an Alias of the Custom TableIn our setup, the first tab functioned correctly, but the 2nd tab would indeed error when trying to update. When using baseline tables (like non_part_usage), we've been able to employ several aliases without encountering update issues.
Hi,I drafted up the following to help get you started on this, there’s other methods, and the coding needs work, but I’m hoping this better explains how I would have set up the code in Scheduled Processes. in this case I did statically code the dates - to make it dynamic, i’m not sure if there’s a code way directly in XML, but worst case validate against the view, which could add a SQL level constraint to only have results for Dispatches due “tomorrow”. Again; just a draft - not tested - possibly not the final answer either. <mass_update_c_sms_day_before_batten_installation> <hierarchy_select result_name="csbbiv"> <attrs> <attr>task.task_id</attr> <attr>c_sms_day_before_batten_installation_view.*</attr> </attrs> <primary_table>task</primary_table> <from> <table>task</table> <table>c_sms_day_before_batten_installation_view</table> </from> <where>
Have you considered using Scheduled Processes instead of, or in addition to, Business Rules?We have a few processes that perform similar functions:Execute a Scheduled Process daily at 8 AM.The XML within the process either processes what we need or updates a value, or creates an event, on the relevant record. Subsequently, a Business Rule utilizes this event or value to generate notifications. Sincerely,-Rudy
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
