Limitations related to Excel import/export
The possibility to import or export Excel files into or from the application is a key functionality of the beqom platform. It enables users to export business data and use these data offline. beqom offers two types of export to Excel:
Basic process export: this feature enables you to export the data of a process grid, in a raw format, without macros and without logic (data operations, conditional validation, drop-down lists, etc.), in the state in which the process currently exists in the application. This type of export results in an Excel file that can be easily manipulated and used for modeling as a means to facilitate decision-making in the beqom application. Files exported using the basic export feature cannot be reimported into the beqom application.
Standard process export: this feature (which is the historic type of export offered in the beqom application) enables you to export a macro-enabled field that mirrors the process grid as it is in the beqom application, with all the logic applied to the grid. This type of export can be used to actually work on the process grid offline before reimporting the data into the beqom application.
Due to the complexity of the feature, some limitations apply to both the basic export and the standard export, depending on the context in which the features are used. This article details these limitations.
Excel Export Limitations - Basic Export
| Functionality | Limitation(s) | Comment |
|---|---|---|
| Quick Filters | Quick filters are not applied when exporting a process grid using the basic export feature. |
|
| Calculated formulas with hidden information fields | A process with calculated formulas containing hidden information fields for a given profile will return 0 values in the calculated fields in Excel. | beqom recommends to make the hidden information fields visible in order for the basic export feature to return the correct values in Excel. |
Excel Export Limitations - Standard Export
The following table lists all the limitations that are currently known about the standard Excel export functionality and the application feature to which each limitation is related.
| Functionality | Limitation(s) | Comment |
|---|---|---|
| Process grid aggregated view | No UI to configure. | |
| Summary view calculated fields can only be based on aggregated values. | ||
| Custom Excel export layout | Customization of the header is limited to the background color of the cell. | |
| Quick Filters | Quick filters are not applied when exporting a process grid using the standard export feature. | |
| Conditional validation in Excel |
Colors not configurable:
|
|
| Conditional editability in Excel | Conditional editability is not supported in Excel exports. When the grid is exported to Excel, the fields to which conditional editability is applied are editable. | |
| Data Operations | Support is limited to data operations of "calculate" type. | If the data operations are configured with a parameter that is not supported, specifically, data operations with multiple steps, the beqom application will allow you to export, but the Excel file will not be useable (crashes are to be expected). |
| The maximum length of the formulas is 255 characters. | ||
| Multiple steps in one data operation are not supported. | ||
|
Circular data operations (for instance when two columns are associated so that entering a value in column A will update column B, and entering a value in column B will update column A, according to a defined formula) are not supported. | ||
| If a value is not defined, the system considers it as 0. | ||
| If the calculation of a formula fails (for instance, in an attempt to divide by 0), then a generic alert is displayed. This error can neither be customized nor deactivated. | ||
The system assumes that all the columns used in data operations are numeric fields. It is the responsibility of the admin to make sure that the data operation is properly configured. | ||
| The only way to update data in bulk is to copy/paste values withing Excel. Cursor drag and drop does not trigger the calculation macro, which means that the data operation is not triggered. | ||
| Circular dependencies are not supported in Excel. | ||
| Cascading Fields | Cascading fields are not supported in Excel exports; they are exported as read-only. | |
| SSRS Reports | Exporting an SSRS report will fail if the operation takes longer than 3 minutes 50. | This is an Azure-related limitation. More information on the topic is available here. |
| Data Entry | It is not possible to copy/paste formulas and functions into an exported Excel file with macros. Only values can be pasted into Excel exports. | Attempting to paste a formula or a function into an exported Excel file with macros will cause an error. |
Excel Import Limitations
The following table lists all the limitations that are currently known about the Excel import functionality and the application feature to which each limitation is related.
| Functionality | Limitation(s) |
|---|---|
Import into the beqom application |
When a process grid has been exported to Excel using the standard import feature, it is not possible to delete columns and rows in the exported file and then re-import it into the application. The macro prevents this action. |
| When a process grid has been exported to Excel using the standard import feature, it is not possible to add columns and rows in the exported file and then re-import it into the application. The macro prevents this action. | |
| When a process grid has been exported to Excel using the standard import feature, it is not possible to copy/paste the data to another sheet of the same Excel file and re-import it into the application. The macro prevents this action. | |
| When a data grid has been exported to Excel using the standard import feature, it is not possible to add/remove columns in the exported file and then re-import it into the application. Rows can however be added. | |
| When using exporting a data grid into Excel with macros, the Excel file cannot be used as a backup for the grid. Only a template can be used as a backup. This means that, if a value is changed in Web App, reimporting the Excel file without any changes will not restore the initial value in Web App. | |
| It is not possible to load only certain columns of an Excel file. | |
| When importing in the Web App, the order of the columns in the Excel file must match the order of the grid in the application. |