Considerations for entity action tracking

Keep in mind the following potential issues when using entity action tracking:

• Each action you track requires a record to be written to the eConnect_Out table in the database. If you track multiple actions for a business object that is used frequently, application performance could be impacted. Turn on entity action tracking only for the actions that you need to track.
• It is up to you to decide when the records in the eConnect_Out table are no longer needed and can be removed from the table.
• When accessing entity action tracking information, you may see actions that you didn't expect. For instance, when an item is created in Microsoft Dynamics GP, you would expect a create action to be logged. However, an update operation is also logged. This occurs because Microsoft Dynamics GP first creates the item, and then updates it with the information the user entered.