We are pleased to announce support for specifying a user role when configuring Snowflake connections, a new API endpoint for purging deleting records, and other improvements.

Snowflake Connections: Support for Snowflake Role

You can now specify the user's role to use when connecting to Snowflake. Ensure that this role is used for Tamr only and has permissions to access the necessary tables in Snowflake. If a role is not supplied, the user's default Snowflake role is used.

See Requirements for Snowflake for more information about configuring Snowflake connections.

Tamr Cloud APIs: Purge Deleted Records

You can use the new Record History endpoint to purge deleted record data from the system and to retrieve details of purge operations.

See Record History for more information about using this endpoint.

Bug Fixes and Other Improvements

• B2B Company 360 pages now include a badge indicating how the company was verified against Tamr’s firmographic corpus.

  

• Improved auto-mapping for address, phone, and email attributes on the Configure Data Product page.

• On the Sources page, Last Updated date is now a separate, sortable column.

• Removed the Applied Rules column from the Source Records page. This column showed the zero-indexed number of the first clustering rule applied to the record. The existing Applied Clustering Rules column provides more complete information about all applied rules, including the number of the rule and attribute. For existing data products, the Applied Rules column will be removed from the Source Records page the next time the data product is refreshed.

• Resolved an issue in which an entity’s verified source record count was not updated when verified source records were deleted.

• General usability and performance improvements.