In the Analyst tool, drilldown on a column with Date data type fails when the following conditions are true:

You choose Oracle JDBC connection for the profiling warehouse.
You choose a JDBC connection to connect to a source to import a table.
You create and run a column profile on the table.

When you enable operating system profile and drilldown on the column profiles or scorecard results, the drilldown sometimes fail.

In Informatica Analyst, you cannot export profiles and scorecards if the pop-up blocker is enabled for the browser.

The detail view for a column with data type Decimal takes a long time to appear if the profiling warehouse uses Microsoft SQL Server database.

In the Analyst tool, you need to check in a profile after every edit to run a profile but you can edit and run a scorecard multiple times before you check in the scorecard if Team-based development is enabled.

An error appears after you perform a query on the MRX_PROFILE_RULES view if the Model repository uses Microsoft SQL Server and Microsoft Azure SQL database.

Create, open, and run profiles or scorecards takes a long time if the Model repository uses Microsoft Azure SQL database.

In the Developer tool, when you run a column profile on a JSON data object, some fields might not appear in the profile definition or profile results.

An exception appears when you run a column profile on an Avro or Parquet data object in Amazon S3 bucket.

An error appears when you create a column profile on an Avro data object that contains an array data type.

When you run a column profile on a JSON data object, the special characters !, @, #, $, %, ^, & , and * in the column field names are replaced with underscores in the profile definition and profile results.

When you run a SQL query that uses the MRX_SC_RULE_METRICS view, the query results appear after an indefinite period of time.

In the Developer tool, when you create a column profile on a logical data object and add a filter to the profile, the filter preview does not appear.