Displayr

Some table outputs throw an error in red and are put in an error state if they are empty (versus native tables that display a “no data” message). In this case, all of the dependencies of the table output (in this case an autofit table) will also show as in an error state and the cached previous results are shown. The user wanted the table that was dependent to be blank or show an error message rather than showing the cached results. In order to do this, you need to edit the R code of the first table to use tryCatch() and suppress the “ERROR” and then edit the second table’s R CODE (which errors because the first table is empty) with the same function so that both tables just return blank/a custom error message if they’re in error. Would be great if there could be a checkbox which would suppress the error _state_ of the output if desired so further error handling could be done down further in the dependency chain.

There should be a global setting that allows users to turn off warnings.

A user has a QDat file that takes time to automatically update when schedules are set to update on server start. The updating of the QDat file and other items that might use the same schedule takes time and sometimes prevents users from being able to republish a dashboard (throwing an error instead). The suggestion is to provide a status bar or alert once everything is done updating/recalculating in the document to let the user know that it's safe to perform other actions. Similar to the request here: https://displayr.canny.io/displayr/p/add-a-progress-bar-or-other-feedback-to-long-running-operations

Currently, if a document has an error in the scheduler, the user sees a small orange icon in their document name, or they can see there's an error when having the Schedules pane open in their document. It would be helpful if we also put the error message in a more visible/obvious place directly in the document, such as a red or orange pinned icon in the Tools section of the toolbar to alert that there's an issue and the same icon next to Schedules option in the dropdown. It would also be nice to either list out the errors within the schedules pane OR put a link to the document errors, which will open in a new tab. Another idea is to send an email notification to the document owner or those who have editing rights to let them know that there's an issue. Thinking about a company like GfK who has hundreds of Displayr documents, they may not realize that there is a scheduler issue unless they happen to be scrolling through their very long documents list or within a specific folder where the errored document is placed. Otherwise, they may never know that there's a problem until well after it initially occurs.

This suggestion is to have Displayr provide a notice or warning message in the application prior to upgrading the version. The user will appreciate a short notice period (say 5 minutes) for them to stop what they are doing and go grab a coffee. Currently, the upgrades just happen. Usually it is a brief interruption. However, if the user is in the middle of typing, or if they are doing text coding, the app upgrade could be a more significant interruption. In text coding, it may cause them to lose some work.

Primary suggestion: There have been multiple occasions where I've been working on a document and another user has gone to the version history and reverted the document, causing a loss of work without any immediate explanation so it'd be good to have a little warning so that the user isn't met with confusion and shock. Secondary suggestion: Issue - Even if I were to create a copy of the document prior to reversion to try and salvage what was lost, that pre-reversion version may not be up-to-date and a loss of work is inevitable. This also isn't a viable solution for documents with larger data files Suggestion - Reversion needs to be opted in by everyone who is currently active in the document

The client was warned about the object size where {{QAllowLargeResultObject}} was referenced. I initially thought I had to change the R code in Displayr. It turns out you can just increase the size in the object inspector. Can we change the warning so users know they can make the change in the object inspector?

When adding variables as columns to tables, if a variable is not compatible, have a warning show up for the end user.

The user would like a warning added to Displayr when deleting a page to avoid deleting it by mistake.