Sage PSA and Smart Rules

This article provides key information on Sage Intacct Smart Rules and Sage PSA. 

• Sage Intacct Smart Rules

Sage Intacct Smart Rules

Sage PSA does not support Sage Intacct Smart Rules. 

If your Sage Intacct installation relies on Smart Rules associated with any of the data points supported by Sage PSA, functionality resulting in changes in Sage Intacct may not work. These could include failure to export/sync data from Sage PSA to Sage Intacct.

• For example:
  • A Smart Rule enforcing the definition of Project Type in Sage Intacct will fail to import any project from Sage PSA into Sage Intacct due to Sage PSA not supporting Project Type.

Projects, tasks, and timesheets/timesheet entries are the entity objects involved in the supported flows between Sage PSA and Sage Intacct that may be impacted by Smart Rules in Sage Intacct.

The operations to which Smart Rules are added that could impact the supported flows are as follows:

• Tasks: Set, delete, add
• Projects and Timesheets/Timesheet Entries: Set, add

If you encounter any issues where smart rules have been applied, you must modify the rules to ignore Sage PSA operations. This can be achieved by incorporating an extra condition that checks if the operation was carried out by the same user ID that was used to enable the Sage PSA connection originally where <user id> should be the relevant username. Your smart rules should be evaluated to True if the following condition is met. 

{!USERPROFILE.LOGIN!} == "<user id>"

Ensure that your Web Services user is only used for web services to apply smart rules correctly. To prevent your smart rules from breaking, avoid performing operations via the Sage Intacct interface using the same user ID that enables the Sage PSA connection.