Migrating Reports to Google Sheets

When migrating Jedox Web Spreadsheets or Excel reports to Google Sheets, you must adjust formulas for function naming restrictions and design for API constraints.

Differences in the naming of functions

Google Sheets does not allow periods in custom function names. You must manually replace these periods with an underscore (_). Use Google's "Find and Replace" (CTRL+H > CTRL+F) feature to make this change efficiently.

WSS / Excel Google Sheets
=PALO.DATAC("localhost/Demo","Sales","All Products","Europe","Year","All Years","All Versions","Units") =PALO_DATAC(trigger,"localhost/Demo","Sales","All Products","Europe","Year","All Years","All Versions","Units")
=PALO.ESELECT("localhost/Demo","Products","All Products",0,,,,) =PALO_ESELECT(trigger,"localhost/Demo","Products","All Products",0,,,,)

Array-based functions and import behavior

When importing PALO functions that are based on arrays, Google Sheets may automatically insert the ARRAYFORMULA or ARRAY_CONSTRAIN and add numerical coordinates at the end of the formula. Manually adjust the formulas after importing by removing these additions, replacing periods with underscores, and triggering a recalculation.

Original (Jedox Web / Excel):

=PALO.SUBSET("localhost/Demo";"Products";1;;;;;;PALO.DFILTER(PALO.SUBCUBE("Sales";"Germany";"Jan";"2027";"Approved";"Units")))

Imported into Google Sheets:

=ARRAY_CONSTRAIN(PALO.SUBSET("localhost/Demo";"Products";1;;;;PALO.DFILTER(PALO.SUBCUBE("Sales";;"Germany";"Jan";"2027";"Approved";"Units");8, 1)))

Modified and compatible:

=PALO_SUBSET(trigger,"localhost/Demo";"Products";1;;;;;;PALO_DFILTER(PALO_SUBCUBE("Sales";;"Germany";"Jan";"2027";"Approved";"Units")))

Key constraints and design considerations

The following constraints are inherent to the Google Sheets Add-on API and beyond Jedox's control. Consider these when designing reports and planning migrations:

  • No batch processing — Each PALO call triggers a separate network request.

  • API quota limits — Google Sheets enforces a limit of 300 API calls per minute. Each PALO custom function triggers one API call. We strongly recommend array-based functions (e.g., PALO_DATAV, Subset functions) because a single function can return multiple values, requiring only one API call instead of many. Reaching the quota limit can significantly slow down or block recalculation.

  • Execution timeout — Custom functions must return within 30 seconds; otherwise, Google Sheets displays the error message #ERROR. If the Jedox server takes longer than 30 seconds to respond, Google Sheets may display error messages during recalculation.

  • Limited formula support — Google Sheets does not provide a built-in function editor or inline help for custom functions. When typing PALO functions, no argument descriptions or guidance are shown. Auto-complete is limited to a small, non-scrollable list (up to 10 entries). Although more than 10 PALO functions are available, they display as you continue typing and refine your search.

Adoption guidance

The Jedox Add-on for Google Sheets is particularly well-suited for simple reports and reports of low-to-medium complexity, especially those based on array formulas. For successful implementation, adapt your report design to the execution and performance constraints of Google Sheets.

 

Updated October 19, 2026