Accessing Planning Analytics Workspace from Apple iPad
When you log in to Planning Analytics Workspace from an iPad, you are always working in Consumer mode, regardless of your actual defined role assignment.
In Consumer mode you can:
- Open the Welcome page and view the folder structure
- Open existing views, books, and websheets
- Change cell formats
- Switch visualization types
- Interact with explorations and visualization (drill down, hide members, reorder dimension, and so on)
- Use selectors to set context for explorations and visualizations
In Consumer mode on a mobile device, you cannot:
- View or access the data tree
- Use or enable Edit mode
- Perform any administration tasks
- Save an existing view or book, or use save-as to create a copy of a view or book
- Create a view or book
- Open the Set Editor to modify existing sets or create new sets
- Create member calculations or summary calculations
- Share a book or view in any manner (download, email, or print)
- Delete or rename a book or view
- Add a view to a collection
In addition, you cannot create conditional formatting on an iPad.
Performance considerations
When you open a view on an iPad, Planning Analytics Workspace initially loads and displays only the number of rows that fit on a single page. Depending on how the view is configured, this can be anywhere between 30 - 50 rows.
As you scroll through the view, Planning Analytics Workspace loads each subsequent page sequentially. This occurs even if you rapidly scroll through several pages without pausing for each page to be displayed. For example, if you are looking at a value on the first page of a view, and then scroll to page 8 of the view, pages 2 - 7 must be loaded before page 8 can be displayed. There is a slight delay as each page is loaded.
To maintain minimal load times, limit views that are accessed from iPads to 120 or fewer rows.
Additionally, you can improve performance by:
- Limiting the number of views on a single sheet (the best performance is achieved with a single view on a sheet)
- Using chart visualizations in place of explorations (grids) whenever practical
- Limiting the scope of synchronization between views to the lowest possible level