As I understand it, current platform infrastructure only allows X number of records to be bulk updated at once. Curious if Ironclad is working on improving this.
For example, I'm going through to bulk update permissions on records by "Department"/group. Some of our groups have thousands of records, which Ironclad (apparently) can't handle at once. The system notifies you of this (see below example), but there is no rhyme or reason behind which records didn't make the cut for the update, so now I'm left with a random amount of records that didn't benefit from the update, and no feasible way to correct that.
The workaround that has been suggested is to filter by each record type for each department to make the views smaller for updating. What if a single record type has more than the limit of records that can be updated at once? Are we supposed to find other fields to filter for instead? This "workaround" is pesky and not scalable. It would be ideal for the infrastructure to just allow unlimited - or a much larger - number of records to be bulk updated at one time. Would love for Ironclad to be able to overcome this.
