RConnect Shiny Dashboard rendering DataTables Warning says: Table ID = DataTables_Table_0 - Ajax error about dt HOT 5 OPEN

No idea, your code is not understandable without more contextx Regarding the aternatives, there is reactable and gt.

from dt.

Hi All,

I am with Posit support and have been working with @babu-g to try and fix this issue. A number of staff have looked at this and we are not sure where the issue was coming from but we noted it was similar to an old issue here: #266

We are wondering if there are circumstances that could re-trigger this issue in more recent versions. Please feel free to reach out to me via the Posit slack if you have any questions about this case from us.

Thank you!

--Jessi - Support Engineer - Posit PBC

from dt.

@babu-g The "Ajax error" could have many reasons, and it's hard to know without a reproducible example. The Shiny Code.txt you provided is not a reproducible example---we don't have ed_df_11.csv. You have output$summ_table <- DT::renderDataTable(...) in your server function, but summ_table is not present in the ui function, so the table won't be rendered at all.

Please also try to minimize the example. For example, remove packages that are not actually used in the example. Ideally, the example should use DT only, so we can be sure the problem is not caused by other packages, e.g., ggplot2 and plotly should be irrelevant. Keep deleting code until the problems goes away, and then you will be much closer to the root of the problem. For now, it's too hard to tell.

We tried using Google Chrome's Developer pane to check for the error, but the server responded with some 500 - internal error.

500 typically indicates an R error occurred. For security reasons, the error won't be shown in the JS console. You have to check the server log in Connect to see what happened.

from dt.

Hi @yihui ,

Thanks so much for looking into this and clarifying. I am hoping that @babu-g will clean up the sample and retest soon. In the meantime regarding:

500 typically indicates an R error occurred. For security reasons, the error won't be shown in the JS console. You have to check the server log in Connect to see what happened.

I did a sweep of the logs and the Connect dev team checked behind me and they didn't see anything pertinent to the issue either. Do you know what kind of output we should be looking for? I am happy to check again and see if that sheds any light on this issue.

Appreciatively,

Jessi

from dt.

Okay, if there isn't anything pertinent to the issue in the Connect logs, I'll definitely need a minimal reproducible example before I can investigate the problem.

from dt.