Collectors
      Back to home
      1. Knowledge Base
      2. Connect & Transform
      3. Collectors

      Sage Intacct REST Collectors

      Overview

      The Sage Intacct REST collector allows you to collect data from configuration in the Sage Intacct environment. The Sage Intacct account used by DataBlend must have permission to access the desired data.

      Configuration

      Field

       

      Required/ Optional

       

      Comments

       

      Type

      Required

      Sage Intacct REST

      Name

      Required

      Descriptive free-text name for the collector

      Data Source

      Required

      Select a pre-configured data source from the drop down or click Create New to create a new data source.

      Schema Name

      Required

      Enter a name for the schema where the collected data will be stored. This can be a pre-configured schema or a new schema which will be created the first time the collector is run.

      Credential

      Required

      Select a pre-configured Sage Intacct REST credential from the drop-down.

      Intacct Rest Collector Type

      Required

      Select Query from the drop-down menu.
       To learn more about Sage Intacct API requirements, please visit API Reference.
       

      Bookmarks

      Bookmarks can be used on certain collectors to set a dynamic value each time the collector runs. A field from the collector source will need to be selected to be associated with the Bookmark function. For example, ‘WHENMODIFIED’ is a field in the Sage Intacct GL Detail object that can be used as a Bookmark:image-20220816-144337

      Once the Bookmark Field is set, every collection will save the value based on the latest run time. In the example above, the Bookmark is stored as a 'WHENMODIFIED' date of '05/17/2022 04:22:10'. The next time the Collector runs, it will only pull values with a different value, and then will update the Current Value field dynamically.

      Other Notes about Bookmarks:

      • Most commonly set as date fields, the Bookmark Field can also be a non-date field.

      • Filters on the collector can still be applied, so even though a Bookmark may be set, if a filter is present it will still only collect data with both the Bookmark value and filters in mind.

      • Data gets collected into a new stream even when Bookmarks are present, the data does not automatically consolidate into one stream. Consolidation would need to be done in a query.

        • To accomplish this consolidation in the query, your FROM section will need to leverage ‘All Streams’. This will also carry a risk that if the bookmark’s ‘Current Value’ is cleared or the bookmark is removed, the same data can be included into a new stream and therefore overstate the dataset that is being used in the query. It is important to be mindful of which collectors and queries are relying on the bookmark functionality and avoid modifying the bookmark while in use. To reset the bookmarked data, make sure to clear the ‘Current Value’ and also purge all streams or create a new Schema so that you’re starting from an empty dataset.

      Filter types

      Equal To / Not Equal To - For filtering for single value in a field

      In / Not In - For filtering for multiple values in a field

      Like / Not Like - For filtering based on a string value in a field, can be used for a partial match. Ex.: %payment%