Only a user’s view access rights are relevant for the synchronization. Bottom-up access rights (where the access rights depend on sub-tables) are performance-intensive, e.g. "companies with a linked SB record where the user is entered as a rep" or "companies that had contact with the user in the last 2 years". Multiple combinations of such bottom-up access rights result need more resources to process.
Try the following approaches (which can be combined):
Simplification: Edit the access rights so that they are easier to evaluate, the trade-off being a semantic change to the access rights definition. Usually, data exists that the user may not view (set A), data that the user may view but is not interested in (set B) and data that the user may view and is interested in (set C). In this case, you can try to simplify the access rights for set B. The user still cannot view set A while having a complete full view of set C.
Pre-triggering: Access rights can also be simplified by using triggers that create the necessary access information upon saving the record. In an extreme case, a record could exist in a child info area for each FI record and the user is allowed to view the record. In this case, reduce the access rights to a single bottom-up condition. However, triggers need to be used to ensure that these child info areas are kept up to date.
Measures that simplify access rights not only improve the performance of CRM.pad's synchronization but also the performance of queries in all applications that access the Aurea CRM database.