Warning: Error in tempVarsPromiseDomain: argument "name" is missing, with no default

[stanvdbiezen]

library(tidyverse)
library(dplyr)
library(rvest)
library(xml2)
library(gdata)
library(shiny)
library(DT)
library(readxl)
library(writexl)
library(readr)

Dashboard <- read_delim("Dashboard.csv", 
                        ";", escape_double = FALSE, trim_ws = TRUE)
Dashboard$Country<- str_remove_all(Dashboard$Country, "�")
all_countries <- unique(Dashboard$Country)

ui<-fluidPage(
  
  selectInput(
    inputId = "Countries",
    label = "select country",
    choices = all_countries,
    multiple = TRUE),
  
  dataTableOutput(outputId="UCI-Ranking")
)

server<- function(input,output){
  
  output$UCI-Ranking <- DT::renderDataTable(Dashboard)({
    
    country_selected <-Dashboard %>%
      filter(Country %in% input$Countries)
    
    DT::datatable(data = country_selected)
  })
}

shinyApp(ui=ui,server=server)

[EconomiCurtis]

Your demo app refers to a Dashboard.csv that no one will have access to.
If you google that error message, you'll see it has to do with DT. But it's hard to diagnose things without being to setup Dashboard

Could you format this into a reproducible example? That is a set of code or rstudio.cloud project that folks can easily get up and running to replicate your issue? Currently, this is only part of a shiny app.

IF you aren't familiar with best practices for shiny reprexes, check out

Shiny debugging and reprex guide

Shiny issues can be challenging to resolve relative to other problems with your code or statistical methods. Shiny apps are often large, complex projects with interacting files. When seeking help from others it is considered polite to: First, do your best to work through RStudio's debugging tools to diagnose your issue on your own. Often those shiny logs and tracebacks are useful to others trying to help out. Second, strive to minimize the effort required to replicate your issue. You can do this with a reproducible example ("reprex"). Shiny Debugging Errors in Shiny code can be difficult to track down. If you don't know where your problem is coming from, you can track it down with some o…

This will make it easier for folks to replicate your issue and offer suggestions to solve it.