ContributionsMost RecentMost LikesSolutionsRe: Quickbase action limits ?Mark, Would you know if there a way to retry? It would be really bad if there was no way for the system to give a breather and retry or atleast allow for manual retries later. How long are these blocked for once the threshold exceeds ? For ex. Is it counting 10 active webhooks at any given second or looking at if 10 of them were fired at exactly the same second ?Re: Set record level accessActually Mark, your recommendation worked quite well for me with a slight variation with which i was able to apply to Role based record visibility rules. Basically i created a summary field "# of Open Tasks For Current User". The rule was to simply check this to be greater than 0. This rule only applies to roles that are serviced by external vendors. Thanks for getting me pointed towards the right direction.Re: Set record level accessHi Mark, that option sounds interesting. Basically you are saying that if i can create "# of tasks" assigned to the current user, then hide everything. let me think through that. Again it feels like it's obscurity but i guess it probably will work :-)Re: Set record level accessYeah. But this causes data security issue. We wouldn't want the partners to know anything about the projects they are not supposed to know about. I am certain someone has definitely come up with this issue. I know i can fix this using custom scripting / API but i am trying to see if there's a way to deal with this without having to go through that. It appears like Quickbase has tied our hands behind our backs in these type of scenarios. I would have thought this is project management 101 issue.Set record level accessHi, I have an issue i am grappling with on how to implement within Quickbase. The App is a high level project management app with multiple tasks. Project record is the base record that contains details about the project. A project can have multiple tasks and each task can be performed by a different outsourced partner. They are not the ones creating these tasks. Tasks are pre-created and assgined to the respective partner company (assumption is there's max of one of two people from each partner company that'll have quickbase logins). So far so good. I have been able to create template records that determine the partner companies the project tasks will be assigned to. With that logic i can easily control which partner company sees which task record using custom rule on the role. Now my issue is with the parent project record itself. What method can i employ to limit the view of the project record to only the partner companies assigned in the task. At any given point in time there could be 10-12 partner companies working on any given project. Reverse relationship is really not an option as a partner company could be working on more than one task. Moreover not all tasks have pre-determined assgined company. Sometimes someone can manually assign a task or re-assign it. Basically what i really need i think is a way for me to concatenate all partner ids and make it visible to the project record. I havent seen any native way of making this happen. Any ideas/thoughts on how i can make this happen ? Thanks!Re: Quickbase action limits ?I read somewhere that it's 10 + 10. They are counted differently from what i understood.How safe is BOL technique?Hi Dan, I have been reading the BOL technique and it appears it is built on the concept of probably hacking, for the lack of a better word "vulnerability" or open patch within quickbase. Is that true ? If so, do you think that technique will be around for long ? I know the alternate is the SW technique. The only issue i see with that technique is that it prompts the user for participation and hence we are at their mercy. Given the issue with the user having to opt in for SW, i was looking for an alternate way to have branding change done across the application and the only one that seems to come close is the BOL. But i am worried on the logevity of the solutions. What are your thoughts on the subject ? Thanks!!Re: Service Worker to the Rescueok. no worries, looks like you updated it.Re: Service Worker to the RescueDan, it appears both the links above are to the same page. Could you send me the one where you are adding the script tag ?Re: Service Worker to the RescueBut Dan, if we have the need to do DOM based adjustments (such as adding a new div element etc), for that we have to wait for the DOM to fully load and only then we can perform the necessary javascript based alterations. how will we do all that with a service worker ? In the service worker, we are intercepting fetch requests which is way before the DOM is even loaded in the browser. right ?