Skip to main content

Known Issues

Export Not Supported on Windows Azure App Service​

Issue​

When hosting on Azure App Service (Windows), exporting is not supported. This is because Playwright, required for browser-based exporting, is not supported on Windows distributions within Azure App Service.

Workarounds​

There are two options to resolve this:

  1. Use a Linux App Service Plan Host your app on Azure App Service (Linux) instead of Windows. In your ASP.NET Core startup, call the Playwright installer during application startup—typically in Program.cs, before running the web application:

    var builder = WebApplication.CreateBuilder(args);
    //...

    Microsoft.Playwright.Program.Main(new string[] { "install", "chromium", "--with-deps" });

    app.UseAuthorization();
    app.MapControllers();
    app.Run();

    This ensures Chromium and all required dependencies are available at runtime.

  2. Use a Windows Container If you must remain on Windows, host the application inside a Windows Container. This allows installing and configuring Playwright within the container image, bypassing the Windows App Service limitation.

<Pre> Tag Appended to <body>​

Issue​

The RevealView component appends a hidden <pre> tag to the end of the <body> element. This tag is used internally by the viewer to measure font sizes for layout calculations. If the your application includes CSS rules targeting <pre> elements (e.g., global typography or spacing styles), these rules may inadvertently apply to the RevealView measurement element. This can lead to unexpected visual artifacts or layout shifts in the UI.

Workarounds​

To prevent these unwanted styles from affecting the measurement element, add the following CSS rule to your global stylesheet:

body > pre.rv-multiline-editor {
    height: 0px !important;
}

Grid Row Paging​

  • Paging is supported in the following providers: SQL Server, MySQL, BigQuery, MongoDB, PostgreSQL, Snowflake, SyBase, Redshift, Databricks, Cube.dev, Athena, and Oracle.
  • Providers that support stored procedures will have grid paging disabled when a stored procedure is selected as these can't be queried like tables to return a range of rows.
  • Paging is not available when processing data on server is false
  • When sorting a grid with paging enabled in regular view mode the column sorts will be applied from left to right. This means if you sort the last column and then sort the first column, they won't be applied in that order, but rather from left to right.

Exporting on Linux ARM64 for Node​

Headless Export​

  • Headless export in Node.js SDK is not available for Linux/MacOSX
  • Headless export fails if DocumentExportOptions is used. Please use the format-specific classes instead (e.g. PdfExportOptions).

Headless Export - Global Filters​

  • XMLA filters are not currently supported in ASP.NET
  • Global filters for Node.js are not currently supported

Licensing​

  • When using the NuGet package, the watermark is still displayed after licensing the Reveal SDK (entering a valid key in the SDK installer). As a workaround, you can uninstall the NuGet package from the project, clear the NuGet’s cache, and install the package again. In the case that you don’t want to clear all NuGet’s cache, you can lookup the location of that cache and clear only the Infragistics Reveal items. The location depends on the NuGet version and whether packages.config or PackageReference is used.

MacOS ARM64 Support (Beta)​

  • There may be locale issues depending on the machine's configuration (e.g. 9,5 vs 9.5)

MongoDB Connector​

  • Blending by a calculated field using the currentTimeZone function fails
  • Blending by a calculated field referencing the _id column fails
  • The concatenate function does not implicitly cast to string the parameters, which might produce errors when evaluating non-string column references / functions
  • A pivot with no fields in row, but one or more dimensions in columns will not produce any rows in the pivot
  • Embeddings are not supported; however, single-valued embeddings are
  • MongoDB version greater than or equal to v5.0 is supported
  • Fields with a dot (".") or a dollar sign ("$") in their names are ignored. Most cases require special treatment: Dot & Dollar Considerations
  • Filtering by a field of type ObjectId
  • When performing a sum that includes null in MongoDB, the result is 0, not null as in SQL server