Hello,
Some medabase system (when I log in with my user) in current dashboard I can see all graph without problems.
But when I open same dashboard in shared public link, I see two graphs with error:
The same two graphs which are connected to date filter in dashboard (but, once again, it works perfectly if I open it not over shared link).
I can see some errors in log too:
Apr 17 15:52:51 DEBUG metabase.middleware :: GET /api/public/dashboard/43e877a3-d307-4fe0-b34e-1856b933eda0 200 (19 ms) (13 DB calls). Jetty threads: 8/50 (3 busy, 6 idle, 0 queued)
Apr 17 15:52:51 DEBUG metabase.middleware :: GET /api/session/properties 200 (4 ms) (1 DB calls). Jetty threads: 8/50 (3 busy, 6 idle, 0 queued)
Apr 17 15:52:51 WARN metabase.middleware :: Invalid param:
Apr 17 15:52:51 WARN metabase.middleware :: Invalid param:
Apr 17 15:52:52 WARN metabase.query-processor.middleware.expand :: You shouldn’t specify an :and filter with only one subclause.
Apr 17 15:52:52 WARN metabase.query-processor.middleware.expand :: The syntax for aggregate fields has changed in MBQL '98. Instead of[:aggregation 0], please use[:aggregate-field 0]instead.
Apr 17 15:52:52 WARN metabase.query-processor.middleware.expand :: You shouldn’t specify an :and filter with only one subclause.
Apr 17 15:52:52 DEBUG metabase.middleware :: GET /api/public/dashboard/43e877a3-d307-4fe0-b34e-1856b933eda0/card/35 400 (11 ms) (3 DB calls).
“An error occurred.”Apr 17 15:52:52 DEBUG metabase.middleware :: GET /api/public/dashboard/43e877a3-d307-4fe0-b34e-1856b933eda0/card/38 400 (17 ms) (3 DB calls).
“An error occurred.”Apr 17 15:52:52 WARN metabase.query-processor.middleware.expand :: You shouldn’t specify an :and filter with only one subclause.
Apr 17 15:52:52 WARN metabase.query-processor.middleware.expand :: You shouldn’t specify an :and filter with only one subclause.
Apr 17 15:52:52 WARN metabase.query-processor.middleware.expand :: The syntax for order-by has changed in MBQL '98. [ :ascending/:descending] is deprecated. Prefer [:asc/:desc ] instead.
Apr 17 15:52:52 WARN metabase.query-processor.middleware.expand :: The syntax for aggregate fields has changed in MBQL '98. Instead of[:aggregation 0], please use[:aggregate-field 0]instead.
Apr 17 15:52:52 WARN metabase.query-processor.middleware.expand :: The syntax for order-by has changed in MBQL '98. [ :ascending/:descending] is deprecated. Prefer [:asc/:desc ] instead.
Apr 17 15:52:52 WARN metabase.query-processor.middleware.expand :: You shouldn’t specify an :and filter with only one subclause.
Apr 17 15:52:52 WARN metabase.query-processor.middleware.expand :: The syntax for aggregate fields has changed in MBQL '98. Instead of[:aggregation 0], please use[:aggregate-field 0]instead.
Apr 17 15:52:52 WARN metabase.query-processor.middleware.expand :: The syntax for order-by has changed in MBQL '98. [ :ascending/:descending] is deprecated. Prefer [:asc/:desc ] instead.
Apr 17 15:52:53 DEBUG metabase.middleware :: GET /api/public/dashboard/43e877a3-d307-4fe0-b34e-1856b933eda0/card/40 200 (1 s) (15 DB calls). Jetty threads: 8/50 (8 busy, 1 idle, 0 queued)
Apr 17 15:52:53 DEBUG metabase.middleware :: GET /api/public/dashboard/43e877a3-d307-4fe0-b34e-1856b933eda0/card/37 200 (2 s) (15 DB calls). Jetty threads: 8/50 (8 busy, 1 idle, 0 queued)
Apr 17 15:52:53 WARN metabase.middleware :: Invalid param:
Apr 17 15:52:53 DEBUG metabase.middleware :: GET /api/public/dashboard/43e877a3-d307-4fe0-b34e-1856b933eda0/card/35 400 (4 ms) (3 DB calls).
“An error occurred.”Apr 17 15:52:53 WARN metabase.middleware :: Invalid param:
Apr 17 15:52:53 DEBUG metabase.middleware :: GET /api/public/dashboard/43e877a3-d307-4fe0-b34e-1856b933eda0/card/38 400 (3 ms) (3 DB calls).
“An error occurred.”Apr 17 15:52:53 DEBUG metabase.middleware :: GET /api/public/dashboard/43e877a3-d307-4fe0-b34e-1856b933eda0/card/36 200 (2 s) (15 DB calls). Jetty threads: 8/50 (8 busy, 1 idle, 0 queued)
Apr 17 15:52:53 DEBUG metabase.middleware :: GET /api/user/current 200 (3 ms) (1 DB calls). Jetty threads: 8/50 (9 busy, 1 idle, 0 queued)
Apr 17 15:52:53 WARN metabase.query-processor.middleware.expand :: You shouldn’t specify an :and filter with only one subclause.
Apr 17 15:52:53 DEBUG metabase.middleware :: GET /api/public/dashboard/43e877a3-d307-4fe0-b34e-1856b933eda0/card/39 200 (2 s) (15 DB calls). Jetty threads: 8/50 (8 busy, 2 idle, 0 queued)
Apr 17 15:52:53 WARN metabase.query-processor.middleware.expand :: The syntax for aggregate fields has changed in MBQL '98. Instead of[:aggregation 0], please use[:aggregate-field 0]instead.
Apr 17 15:52:53 WARN metabase.query-processor.middleware.expand :: The syntax for order-by has changed in MBQL '98. [ :ascending/:descending] is deprecated. Prefer [:asc/:desc ] instead.
Apr 17 15:52:53 WARN metabase.query-processor.middleware.expand :: You shouldn’t specify an :and filter with only one subclause.
Apr 17 15:52:53 WARN metabase.query-processor.middleware.expand :: You shouldn’t specify an :and filter with only one subclause.
Apr 17 15:52:53 WARN metabase.query-processor.middleware.expand :: You shouldn’t specify an :and filter with only one subclause.
Apr 17 15:52:53 WARN metabase.query-processor.middleware.expand :: The syntax for aggregate fields has changed in MBQL '98. Instead of[:aggregation 0], please use[:aggregate-field 0]instead.
Apr 17 15:52:53 WARN metabase.query-processor.middleware.expand :: The syntax for order-by has changed in MBQL '98. [ :ascending/:descending] is deprecated. Prefer [:asc/:desc ] instead.
Any ideas why?
Lukas