Omniscope Help Center

Importing data from XML involves configuring a File block to point to the XML file, then defining rules that map from the hierarchical structure of an XML d...

This is an example of the effects and use case for the Locale setting in the File block. When opening a CSV file, it matters what locale it was created in. ...

Omniscope Evo will have direct Salesforce connectivity in future. Until then, here's another way to access the data in your Salesforce account, as a reg...

Omniscope Evo allows you to pull the data from your Salesforce account to combine it with information coming from other sources, either to create a more com...

Omniscope Evo has the ability to load data from virtually any SQL-compatible database that comes with a JDBC driver. In order to connect and extract the d...

Omniscope needs a OAuth2 client ID and client secret to connect to your Google Analytics data.  You will be registering your Omniscope deployment as a clie...

Omniscope needs an OAuth client ID and client secret to authenticate to your Google account in order to use a Google connector, e.g. Sheet, DoubleClick, Go...

In Omniscope Evo it is possible to import data from, and publish data to Google BigQuery tables via community blocks. Google BigQuery Import Table all...

Introduction Omniscope supports reading and writing data to and from an Amazon S3 bucket. An Amazon S3 bucket is a public cloud storage resource available ...

Introduction Omniscope supports reading and writing Apache Parquet files. This functionality was introduced in a daily build in December 2001, and will ...